<HTML><HEAD><TITLE>Alpine Technical Notes: Configuration and Preferences</TITLE></HEAD><BODY>
<H1>Configuration and Preferences</H1>

<H2><A NAME="pine-conf">Alpine Configuration</A></H2>

There is very little in <EM>Alpine</EM> which <STRONG>requires</STRONG> compile-time
configuration. In most cases, the compiled-in preferences will suit users
and administrators just fine. When running <EM>Alpine</EM> on a UNIX system, the
default built-in configuration can be changed by setting variables in the
system configuration files, <CODE>/usr/local/lib/pine.conf</CODE>
or <CODE>/usr/local/lib/pine.conf.fixed</CODE>.
(Actually, these files can be changed using the configure arguments
--with-system-pinerc=VALUE or --with-system-fixed-pinerc=VALUE.)
The location of the pine.conf file can be changed with the -P command line
argument.
Both <EM>Alpine</EM>
and <EM>PC-Alpine</EM> also use personal (user-based) configuration files.
On UNIX machines, the personal configuration file is the
file <CODE>~/.pinerc</CODE>. 
For <EM>PC-Alpine</EM> systems, the personal configuration file is in
<CODE>$PINERC</CODE> or <CODE>&lt;PineRC registry value&gt;</CODE> or 
<CODE>${HOME}\ALPINE\PINERC</CODE> or
<CODE>&lt;ALPINE.EXE </CODE>dir<CODE>&gt;\PINERC</CODE>.
Or the personal configuration file can be specified with the -p command
line argument.
<P>
All of these configuration files, other than the fixed system
config <CODE>pine.conf.fixed</CODE> on UNIX systems, may optionally
be remote configuration files instead of local files.
This is discussed further in the following section and in
<A HREF="low-level.html#remote-config"><EM>Remote Configuration</EM></A>.

<P>
After the personal configuration, <EM>Alpine</EM> may optionally use
a personal exceptions configuration file which is specified with the
command line option &quot;-x exceptions_config&quot;.
&quot;Exceptions_config&quot; may also be either a local file or a remote
configuration folder.
For Unix <EM>Alpine</EM>, if you don't have a &quot;-x&quot; command line option,
<EM>Alpine</EM> will look for the file &quot;<CODE>.pinercex</CODE>&quot;
in the same local directory that the regular config file is located in.
If the regular config file is remote then Unix <EM>Alpine</EM> looks in the home
directory for &quot;<CODE>.pinercex</CODE>&quot;.
<P>
For <EM>PC-Alpine</EM>, if you don't have a &quot;-x&quot; command line option,
<EM>PC-Alpine</EM> will use the value of the
environment variable <CODE>$PINERCEX</CODE>.
If that is not set, <EM>PC-Alpine</EM> will look for
the local file &quot;<CODE>PINERCEX</CODE>&quot;
in the same local directory that the regular config file is located in.
If the regular config file is remote then <EM>PC-Alpine</EM> looks in the
local directory specified by the &quot;-aux local_directory&quot; command
line argument, or the directory <CODE>${HOME}&#92;ALPINE</CODE>, or
in <CODE>&lt;ALPINE.EXE </CODE>directory<CODE>&gt;</CODE>.
<P>

The syntax of a non-list configuration variable is this: 

<BLOCKQUOTE>
&lt;variable&gt; = &lt;value&gt;<BR>
</BLOCKQUOTE>

If the value is absent then the variable is unset.  To set a variable to
the empty value two double quotes ("").  This is equivalent to an absent value
except that it overrides any system-wide default value that may be set.  Quotes
may be used around any value.  All values are strings and end at the end
of the line or the closing quote.  Leading and trailing space is ignored
unless it is included in the quotes.  There is one variable,
<EM>use-only-domain-name</EM>, for which the only
appropriate values are <EM>yes</EM> and <EM>no</EM>. That's because it is
a variable from the early days of <EM>Alpine</EM> before features existed.
<P>

There is also a
second type of variable, lists.  A list is a comma-separated list of
values.  The syntax for a list is: 

<BLOCKQUOTE>
&lt;variable&gt; = &lt;value&gt; [, &lt;value&gt; , ... ]<BR>
</BLOCKQUOTE>

A list can be continued on subsequent lines by beginning the line with
white-space.  Both the per-user and global configuration files may contain
comments which are lines beginning with a <CODE>#</CODE>. <P>

For UNIX <EM>Alpine</EM>, there are five ways in which each variable can be set.
In decreasing order of precedence they are: 

<OL>

<LI> the system-wide <EM>fixed</EM> configuration file

<LI> a command line argument

<LI> the personal exceptions file

<LI> the personal configuration file

<LI> the system-wide configuration file.

</OL><P>

If the variable is not set in any of those places, there is a default
setting in the source code.
<P>
So, system-wide fixed settings always take precedence over command line
flags, which take precedence over per-user exception settings, which take precedence over per-user settings, which take precedence
over system-wide configuration settings.
<EM>PC-Alpine</EM> has the same list, except that it
does not use a system-wide <EM>fixed</EM> configuration file.
This can be modified slightly by using inheritance, which is covered below.
<P>

You may get a sample/fresh copy of the system configuration file by
running <EM>alpine -conf</EM>. The result will be printed on the standard
output with very short comments describing each variable.  (The online help in
the Setup screens provides much longer comments.) If you need to fix some
of the configuration variables, you would use the same template for the
fixed configuration file as for the regular system-wide configuration
file.  (If it isn't clear, the purpose of the fixed configuration file is
to allow system administrators to restrict the configurability of <EM>Alpine</EM>.
It is by no means a bullet-proof method.) <EM>Alpine</EM> will automatically create
the personal configuration file the first time it is run, so there is no
need to generate a sample.  <EM>Alpine</EM> reads and writes the personal
configuration file occasionally during normal operation.  Users will not
normally look at their personal configuration file, but will use the
Setup screens from within <EM>Alpine</EM> to set the values in this file.  If a
user does add additional comments to the personal configuration file they
will be retained.
<P>

References to environment variables may be included in the <EM>Alpine</EM>
configuration files.  The format is <CODE>$variable</CODE> or
<CODE>${variable}.</CODE> The character <CODE>~</CODE> will be expanded to the
<CODE>$HOME</CODE> environment variable.
For a more complete explanation of how environment variables work, see
the section
<A HREF="config-notes.html#env-variables">Using Environment Variables</A>.<P>

When environment variables are used for <EM>Alpine</EM> settings which take lists,
you must have an environment variable set for each member of the list. 
That is, <EM>Alpine</EM> won't properly recognize an environment variable which is
set equal to a comma-delimited list.  It is OK to reference unset
environment variables in the <EM>Alpine</EM> configuration file, which
will expand to nothing.  <P>

<H3>Remote and Local Configuration</H3>

There are two types of storage for configuration information.
<EM>Local</EM> configuration files are used by default.
These are just regular files on the UNIX system or on the PC.
<EM>Remote</EM> configuration folders are stored on an IMAP server.
The advantage of using a remote configuration is that the same information
may be accessed from multiple platforms.
For example, if you use one computer at work and another at home, the same
configuration could be used from both places.
A configuration change from one place would be seen in both places.
Technical information about remote configuration is in
<A HREF="low-level.html#remote-config"><EM>Remote Configuration</EM></A>.

<H3>Generic and Exceptional Configuration</H3>

If you use <EM>Alpine</EM> from more than one platform it may be convenient
to split your configuration information into two pieces, a generic piece
and exceptions which apply to a particular platform.
For example, suppose you use <EM>Alpine</EM> from home and from work.
Most of your configuration settings are probably the
same in both locations, so those settings belong in the generic settings
configuration.
However, you may use a different SMTP server and INBOX
from home than you do from work.
The &quot;smtp-server&quot; and &quot;inbox-path&quot; variables could be
part of your exceptional configuration so that they could be different in the
two places.
<P>
You can use the command line option &quot;-x config&quot;
to split your configuration into generic and exceptional pieces.
Config may be either local or remote.
<P>
For most people, splitting the configuration information into two pieces is
only going to be useful if the generic information is accessed remotely.
If you already have a local pinerc file with settings you like you may find
that the command Setup/RemoteConfigSetup will be useful in helping you
convert to a remote configuration.
The command line flag
<A HREF="cmd-line.html#copy_pinerc">copy_pinerc</A>
may also be useful.

<H3>Configuration Inheritance</H3>

Configuration inheritance is a power user feature.
It is confusing and not completely supported by the configuration
user interface.
<P>
For configuration variables which are lists, like &quot;smtp-server&quot; or
&quot;incoming-folders&quot;,
the inheritance mechanism makes it possible to <EM>combine</EM>
the values of options from different configuration locations instead
of <EM>replacing</EM> the value.
<A HREF="config-notes.html#config-inheritance">Configuration Inheritance</A>
has more information about how inheritance is used.
<P>

<HR>

<H2><A NAME="gen-conf">General Configuration Variables</A></H2>

The following is a list of all <EM>Alpine</EM> configuration variables, in
alphabetical order.  Note that not all variables apply to all versions of
<EM>Alpine</EM> and that some variables are only applicable in a system configuration
file and some are only applicable in a personal configuration file.
These are configuration <EM>variables</EM>.
<A HREF="#features-conf">Configuration <EM>Features</EM></A> 
are in a separate section.
<P>

<DL COMPACT>

<DT> <A NAME="addrbook-sort-rule"><EM>addrbook-sort-rule</EM></A>

<DD> This variable sets up the default address book sorting.  Currently,
<EM>Alpine</EM> will accept the values <EM>dont-sort</EM>,
<EM>fullname-with-lists-last</EM>, <EM>fullname</EM>,
<EM>nickname-with-lists-last</EM>, and <EM>nickname</EM>.  The default is
to sort by fullname with lists last.
If you use an address book from more than one computer and those
computers sort the address book differently then the sort order
will be the order where the last change to the address book was
made.
There are two reasons the sorting might be different on different
systems.
First, the addrbook-sort-rule may be set differently in the two
places.
Second, the collation rules on the two computers may be different.
For example, one system might ignore special characters while the other
doesn't or one may sort upper and lower case letters together while
the other doesn't.
In any case, the order you see is the order on the system where the
last change was made, for example by an address book edit or a
Take Address command.
<P>
This option is displayed as &quot;Addressbook Sort Rule&quot;.
<P>

<DT> <A NAME="pers-abook"><EM>address-book</EM></A>

<DD> A list of personal address books.
Each entry in the list is an
optional nickname followed by a pathname or file name relative to the home
directory.
The nickname is separated from the rest of the line with whitespace.
Instead of a local pathname or file name, a remote folder name can be given.
This causes the address book to
be a <A HREF="low-level.html#addrbook"><EM>Remote address book</EM></A>.
Remote folder syntax is discussed in
<A HREF="config-notes.html#remote-folders">Syntax for Remote Folders</A>.
This list of address books will be combined with the
<A HREF="#glob-abook"><EM>global-address-book</EM></A>
list to arrive at the complete set of address books.  <P>

<DT> <A NAME="abook-formats"><EM>addressbook-formats</EM></A>

<DD> This option specifies the format that address books are displayed in. 
By default, address books are displayed with the nicknames in the first
column, the fullnames in the second column, and addresses in the third
column.  The system figures out reasonable defaults for the widths of the
columns.  An address book may be given a different format by listing
special tokens in the order you want them to display.  The possible tokens
are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT. More details are included
in the online help for this variable. <P>

<DT> <A NAME="alt-addresses"><EM>alt-addresses</EM></A>

<DD> This option provides a place for you to list alternate email addresses
you may have.
Each address in the list should be the actual email address part of an
address, without the full name field or the angle brackets.
For example:

<P>
<CENTER><SAMP>user@example.com</SAMP></CENTER>
<P>

The matching is case-insensitive, so this would match any of
<SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or
<SAMP>USER@EXAMPLE.COM</SAMP> as well.

<P>
If set, the option affects the behavior of the Reply
command and the &quot;+&quot; symbol in the MESSAGE INDEX, which denotes that
a message has been addressed specifically to you.

<P>
In the default INDEX display
the personal name (or email address) of
the person listed in the message's &quot;From:&quot; header
field is usually displayed except when that address is yours or one of your
alternate addresses.
In that case you will usually see the name of
the first person specified in the
message's &quot;To:&quot; header field
with the prefix &quot;To: &quot; prepended.

<P>
With respect to Reply, the reply-to-all option will exclude addresses
listed here.

<P>
The feature
<A HREF="#copy-to-to-from">copy-to-address-to-from-if-it-is-us</A>
is somewhat related to this option.

<P>
In addition to a list of actual addresses,
you may use regular expressions (as used with grep -E with the ignore case flag)
to describe the addresses you want to match.
<EM>Alpine</EM> will somewhat arbitrarily interpret your entry as a regular
expression if it contains any of the characters
*, |, +, ?, {, [, ^, $, or &#92;.
Otherwise, it will be treated literally.
The feature
<A HREF="#disable-regex">disable-regular-expression-matching-for-alternate-addresses</A>
may be used to turn off regular expression processing regardless of whether or not
special characters appear in the entry.

<P>
A description of how regular expressions work is beyond the
scope of this help text, but some examples follow.

<P>
The entry

<P>
<CENTER><SAMP>.*@example.com</SAMP></CENTER>
<P>

in the alt-addresses list would mean that any
address with a domain name of <SAMP>example.com</SAMP> (such as
<SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered
one of your alternate addresses.
Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with
a backslash, as in <SAMP>example&#92;.com</SAMP>, and a dollar sign anchor ought
to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>.
Complicating things further, the dollar sign
is special in the <EM>Alpine</EM> configuration (it signifies environment variable expansion)
so the dollar sign should be doubled or backslash escaped for <EM>Alpine</EM>'s sake.
Quotes around the whole expression will not escape the dollar sign successfully.
So this example should look like

<P>
<CENTER><SAMP>.*@example&#92;.com$$</SAMP></CENTER>
<P>

<P>
The entry

<P>
<CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER>
<P>

would match
<SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well
as <SAMP>fred@example.com</SAMP>.

<P>
You could match all addresses that look like
<SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the
entry

<P>
<CENTER><SAMP>^fred&#92;+.*@example.com$$</SAMP></CENTER>
<P>

Notice that you have to escape the plus sign with a backslash because plus
is a special character in regular expressions.
If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP>
the expression

<P>
<CENTER><SAMP>^fred(()|&#92;+.*)@example.com$$</SAMP></CENTER>
<P>

would do it, but it would be easier to just add fred@example.com as a
separate entry.

<P>
One more example, a match of all first-level subdomains, is given by

<P>
<CENTER><SAMP>^fred@[[:alnum:]_-]*&#92;.example&#92;.com$$</SAMP></CENTER>
<P>

<P>
Because the regular expression matching is based on an old library
(<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect,
but they should be close.

<P>
This option is displayed as &quot;Alternate Addresses&quot;.

<DT> <A NAME="bugs-add"><EM>bugs-additional-data</EM></A>

<DD> System-wide configuration files only.  Program/Script used by
<EM>Report Bug</EM> command.  Output from the program/script is
captured and attached to the bug report. <P>

<DT> <A NAME="bugs"><EM>bugs-fullname</EM></A>,
<EM>bugs-address</EM>, <EM>local-fullname</EM>, <EM>local-address</EM>, 
<EM>suggest-fullname</EM>, and <EM>suggest-address</EM>

<DD> System-wide configuration files only.  These are used by the bug
report commands which can be accessed from some of the Help screens.
<P>

<DT> <A NAME="busy-cue-rate"><EM>busy-cue-rate</EM></A>

<DD> When <EM>Alpine</EM> is delayed for some reason it usually shows that
something is happening with a small animated display in the status
message line near the bottom of the screen.
This option sets how frequently the characters (for example, a spinning bar)
in the active status message lines are updated.
At most, it can be set to be updated 20 times per second. 

<P>
Setting this value to zero will prevent display of the animations
altogether.

<P>
The option
<A HREF="#busy-cue-spinner-only"><EM>busy-cue-spinner-only</EM></A>
can be used to remove the randomness from this animated display.
<P>

<DT> <A NAME="char-set"><EM>character-set</EM></A>

<DD> This is now obsolete, replaced by three separate variables:
<EM>display-character-set</EM>,
<EM>keyboard-character-set</EM>, and
<EM>posting-character-set</EM>.
See the section on
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for more
details.<P>

<DT> <A NAME="color-style"><EM>color-style</EM></A>

<DD> UNIX <EM>Alpine</EM> only (color is automatically on with <EM>PC-Alpine</EM>).
If the terminal or terminal emulator you are using is capable of displaying
colors, this variable controls whether or not
color will be used in <EM>Alpine</EM>.
If you turn color on and things are set up correctly,
you should see color appear on the screen immediately.
Modern terminal emulators are usually capable of displaying colors.
<P>
This variable may be set to any of the following values:
<P>

<DL>
<DT>no-color</DT>
<DD>Don't use color.
</DD>

<DT>use-termdef</DT>
<DD>In order to decide if your terminal is capable of color,
<EM>Alpine</EM> looks in
the terminal capabilities database, TERMINFO or TERMCAP, depending on
how <EM>Alpine</EM> was compiled.
This is a good option to choose if you switch between a color and a non-color
terminal with the same <EM>Alpine</EM> configuration.
<EM>Alpine</EM> will know to use color on the color terminal because
it is described
in the termcap entry, and <EM>Alpine</EM> will know to use black and white on the
non-color terminal.
<A HREF="config-notes.html#color-config-notes">Color Details</A>
has more information about configuring a termcap entry for color.
This is usually something a system administrator does.
</DD>

<DT>force-ansi-8color</DT>
<DD>Because setting up a termcap entry is confusing and because the
terminal capabilities database is often not correctly configured for color,
this choice and the next may be easier for you to use.
If your terminal emulator responds to ANSI color escape sequences, which
many do, this option will
cause <EM>Alpine</EM> to believe your terminal will respond
to the escape sequences which produce eight different foreground and background
colors.
The escape sequences used to set the foreground colors are

  <P><CENTER>ESC&nbsp;[&nbsp;3&nbsp;&lt;color_number&gt;&nbsp;m</CENTER><P>

where the color_number is an ASCII digit between 0 and 7.
The numbers 0 through 7 should correspond to the colors black, red, green,
yellow, blue, magenta, cyan, and white.
Some terminal emulators use a pre-ANSI scheme which swaps
the colors blue and red and the colors yellow and cyan.
This will cause the default colors to be different, but other than that
things should work fine.
There is also a 9th color available, the last one shown, which is the default
color from the terminal emulator.
When used as a background color some people refer to this color as
&quot;transparent&quot;, which is why the letters &quot;TRAN&quot; are
shown in the color swatch of the SETUP COLOR screen.
The foreground transparent color is shown as
the color of the &quot;TRAN&quot; text.
(The transparent color will not work correctly in a PC-Alpine configuration.)
The escape sequences used to set the background colors are the same
as for the foreground colors except a &quot;4&quot; replaces the &quot;3&quot;.
<P>
Note: With the Tera Term terminal emulator this setting works well.
You should also have the Tera Term &quot;Full color&quot; option turned OFF.
You may find the &quot;Full color&quot; option in Tera Term's &quot;Setup&quot;
menu, in the &quot;Window&quot; submenu.
</DD>

<DT>force-ansi-16color</DT>
<DD>Many terminal emulators know about the same eight colors above
plus eight more.
This option attempts to use all 16 colors.
The same escape sequences as for the eight-color terminal are used
for the first eight colors.
The escape sequences used to set foreground colors 8-15 are the same as
for 0-7 except the &quot;3&quot; is replaced with a &quot;9&quot;.
The background color sequences for colors 8-15 are the same as for 0-7
except the &quot;4&quot; is replaced with &quot;10&quot;.
You can tell if the 16 colors are working by turning on this option
and then going into one of the color configuration screens, for example,
the configuration screen for Normal Color.
If you see 16 different colors to select from (plus a 17th for
the transparent color), it's working.
</DD>

<DT>force-xterm-256color</DT>
<DD>Some versions of xterm (and some other terminal emulators)
have support for 256 colors.
The escape sequences used to set the foreground colors are

  <P><CENTER>ESC&nbsp;[&nbsp;38&nbsp;;&nbsp;5&nbsp;;&nbsp;&lt;color_number&gt;&nbsp;m</CENTER><P>

where the color_number is an ASCII digit between 0 and 255.
Background colors are the same with the 38 replaced with a 48.
The numbers 0 through 15 are probably similar to the 16 color version
above, then comes a 6x6x6 color cube, followed by 24 colors of gray.
The terminal default (transparent) color is the 257th color at the bottom.
Some terminal emulators will misinterpret these escape sequences causing
the terminal to blink or overstrike characters or to do something else
undesirable.
<P>
The PuTTY terminal emulator has an option called &quot;Allow terminal to
use xterm 256-colour mode&quot; which allows PuTTY to work well with
this 256-color setting.

</DD>
</DL>

<P>
There are two other possible color values which may be useful in some
situations.
In the color configuration screens there will sometimes be a color which has
the label &quot;NORM&quot; inside its color swatch.
If this is selected the corresponding foreground or background
<A HREF="#normal-color"><EM>Normal Color</EM></A>
will be used.
Another similar color is the one that has the
label &quot;NONE&quot; inside its color swatch.
The meaning of this setting is that no color changing will be done.
This NONE color is only useful in contexts where <EM>Alpine</EM> is already
coloring the text some color other than the Normal Color.
For example, if the
<A HREF="#reverse-color"><EM>Reverse Color</EM></A> is set then the current
line in the MESSAGE INDEX will be colored.
If one of the index symbols (for example, the Index-to-me Symbol) has the NONE
color as its background then the symbol's foreground color will be used
to draw the actual text but the background color will be the same as whatever
the background color already was.
The color values which end up in the configuration file for these special
values are the 11-character words &quot;norm-padded&quot;, &quot;none-padded&quot;,
and &quot;transparent&quot;.

<P>
The normal default is &quot;no-color&quot;.
<P>
Once you've turned on color you may set the
colors of many objects on the screen individually.
The <A HREF="#color-config">Color Configuration</A> section has more
information, or you may just try it by
running the &quot;Setup&quot; command and typing &quot;K&quot;
for Kolor to enter the color configuration screen (Kolor instead of Color
because C means Config).
Most categories of color which <EM>Alpine</EM> supports are configurable there.
<A HREF="#index-color-config">Index line color</A> is configured separately.
<P>

<DT> <A NAME="composer-word-separators"><EM>composer-word-separators</EM></A>

<DD> This option affects how a &quot;word&quot; is defined in the composer.
The definition of a word is used when using the Forward Word and Backward
Word commands in the composer, as well as when using the spell checker.
Whitespace is always considered a word separator.
Punctuation (like question marks, periods, commas, and so on) is always
a word separator if it comes at the end of a word.
By default, a punctuation character which is in the middle of a word does
not break up that word as long as the character before and the character
after it are both alphanumeric.
If you add a character to this option it will be considered a
word separator even when it occurs in the middle of an alphanumeric word.
For example, if you want to skip through each part of an address instead
of skipping the whole address at once you might want to include&quot;@&quot;
and &quot;.&quot; in this list.
If you want the word-skipper to stop on each part of a UNIX filename you
could add &quot;/&quot; to the list.
The equal sign and dash are other possibilities you might find helpful.
<P>

<DT> <A NAME="composer-wrap-column"><EM>composer-wrap-column</EM></A>

<DD> This option specifies an aspect of <EM>Alpine</EM>'s Composer.  This gives the
maximum width that auto-wrapped lines will have.  It's also the maximum
width of lines justified using the ^J Justify command.  The normal default
is <EM>74</EM>.  The largest allowed setting is normally <EM>80</EM> in order to
prevent very long lines from being sent in outgoing mail.  When the mail
is actually sent, trailing spaces will be stripped off of each line.
<P>

<DT> <A NAME="current-indexline-style"><EM>current-indexline-style</EM></A>

<DD> <A HREF="#cur-il-style"><EM>current-indexline-style</EM></A>.
<P>

<DT> <A NAME="cust-hdr"><EM>customized-hdrs</EM></A>

<DD> You may add your own custom headers to outgoing messages.
Each header you specify here must include the header tag 
(Reply-To:, Approved:, etc.)
and may optionally include a value for that header.
If you want to see these custom headers each time you compose a message,
you must add them to your
<A HREF="#def-comp"><EM>default-composer-hdrs</EM></A> list, 
otherwise they become part
of the rich header set which you only see when you press the rich header
command.
(If you are looking for a way to change which headers are <EM>displayed</EM>
when you view a message, take a look at the
<A HREF="#viewer-hdrs"><EM>viewer-hdrs</EM></A>
option instead.)
Here's an example which shows how you might set your From address
<P>
<CENTER><SAMP>From: Full Name &lt;user@example.com&gt;</SAMP></CENTER>
<P>
and another showing how you might set a Reply-To address
<P>
<CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER>
<P>
You may also set non-standard header values here.
For example, you could add
<P>
<CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER>
<P>
or even
<P>
<CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER>
<P>
If you include a value after the colon then that header will be included
in your outgoing messages unless you delete it before sending.
If a header in the Customized-Headers list has only a tag but no value, then
it will not be included in outgoing messages unless you edit a value
in manually.
For example, if
<P>
<CENTER><SAMP>Reply-To:</SAMP></CENTER>
<P>
is in the list, then the Reply-To header will be available for editing
but won't be included unless a value is added while in the composer.
<P>
It's actually a little more complicated than that.
The values of headers that you set with the Customized-Headers option are
defaults.
If the message you are about to compose already has a value for a header,
that value is used instead of a value from your Customized-Headers.
For example, if you are Replying to a message the Subject field
will already be filled in.
In that case, if the Customized-Headers list contains a Subject line, the
custom subject will <EM>NOT</EM> be used.
The subject derived from the subject of the message you are Replying
to will be used instead.
<P>
It is also possible to make header setting even more complicated and more
automatic by using
<A HREF="#role-config"><EM>Roles</EM></A>,
but if all you want to do is set a default value for a header, you don't
need to think about Roles.
<P>
If you change your From address you may also find it useful to add the
changed From address to the
<A HREF="#alt-addresses"><EM>alt-addresses</EM></A>
configuration option.
<P>
Limitation: Because commas are used to separate the list of
Customized-Headers, it is not possible to have the value of a
header contain a comma.
Nor is there currently an &quot;escape&quot; mechanism provided
to make this work.
<P>
This option is displayed as &quot;Customized Headers&quot;.
<P>

<DT> <A NAME="dead-letter-files"><EM>dead-letter-files</EM></A>

<DD> This option affects <EM>Alpine</EM>'s behavior when you cancel a message being
composed.  <EM>Alpine</EM>'s usual behavior is to write the canceled message to
a file named 
&quot;dead.letter&quot; in your home directory, or
&quot;DEADLETR&quot; when using <EM>PC-Alpine</EM>,
overwriting any previous message.
<P>
If you set this option to a value higher than one, then that many copies
of dead letter files will be saved.
For example, if you set this option to &quot;3&quot; then you may have
files named
&quot;DEADLETR&quot;,
&quot;DEADLETR2&quot;, and
&quot;DEADLETR3&quot;; or
&quot;dead.letter&quot;,
&quot;dead.letter2&quot;, and
&quot;dead.letter3&quot;.
In this example, the most recently cancelled message will be in
&quot;dead.letter&quot;,
and the third most recently cancelled message will be in
&quot;dead.letter3&quot;.
The fourth most recently cancelled message will no longer be saved.

<P>
If you set this option to zero, then NO record of canceled messages is
maintained.
<P>
If the feature
<A HREF="#quell-dead-letter-on-cancel">Quell-Dead-Letter-On-Cancel</A>
is set, that overrides whatever you set for this option.
If this option had existed at the time, then the Quell feature would not
have been added, but it is still there for backwards compatibility.
So, in order for this option to have the desired effect, make sure the
Quell feature is turned off.
<P>

<DT> <A NAME="def-comp"><EM>default-composer-hdrs</EM></A>

<DD> You can control which headers you want visible when composing outgoing
email using this option.
You can specify any of the regular set, any
Rich Header,
or any <A HREF="#cust-hdr"><EM>Customized-Hdrs</EM></A>
which you have already defined.
If you use this setting at all, you must specify all the
headers you want to see, you can't just add to the regular header set.
The default set is To:, Cc:, Attchmnt:, and Subject:.
<P>

Note that the "Newsgroups:" header will be abbreviated in the Composer
display, but should be spelled out in full here.
<P>
This option is displayed as &quot;Default Composer Headers&quot;.
<P>

<DT> <A NAME="def-fcc"><EM>default-fcc</EM></A>	

<DD> The name of the folder to which all outgoing mail goes is set here. 
The compiled-in default is <EM>sent-mail</EM> (UNIX) or <EM>sentmail</EM>
(PC).  It can be set to "" (two double quotes with nothing between them)
to turn off saving copies of outgoing mail.  If <EM>default-fcc</EM> is a
relative file name, then it is relative to your default collection for
saves (see <A HREF="#fold-coll"><EM>folder-collections</EM></A>).  <P>
This option is displayed as &quot;Default Fcc (File carbon copy)&quot;.
<P>

<DT> <A NAME="def-save"><EM>default-saved-msg-folder</EM></A>

<DD> This option determines the default folder name for <EM>Saves</EM>...
If this is not a path name, it will be in the default collection for saves.
Any valid folder specification, local or IMAP, is allowed.  This default
folder only applies when the
<A HREF="#saved-msg-name"><EM>saved-msg-name-rule</EM></A>
doesn't override it.
Unix <EM>Alpine</EM> default is normally
<EM>saved-messages</EM> in the default folder collection.
<EM>PC-Alpine</EM> default is <EM>SAVEMAIL</EM>
(normally stored as <EM>SAVEMAIL.MTX</EM>). <P>
This option is displayed as &quot;Default Saved Message Folder&quot;.
<P>

<DT> <A NAME="disable-these-auths"><EM>disable-these-authenticators</EM></A>

<DD> This variable is a list of SASL (Simple Authentication and Security
Layer) authenticators which will be disabled.
SASL is a mechanism for
authenticating to IMAP, POP3, SMTP, and other network servers.
<P>

<EM>Alpine</EM> matches its list of supported authenticators with the server to
determine the most secure authenticator that is supported by both.
If no matching authenticators are found, <EM>Alpine</EM> will revert to plaintext
login (or, in the case of SMTP, will be unable to authenticate at all).
<P>

The candidates for disabling are listed below.
There may be more if you compile <EM>Alpine</EM> with additional authenticators
and/or a newer version of the c-client library.
<P>

<UL>
<LI> GSSAPI
<LI> CRAM-MD5
<LI> PLAIN
<LI> LOGIN
</UL>
<P>

Normally, you will not disable any authenticators.
There are two exceptions:
<P>

<OL>
<LI> You use a broken server that advertises an authenticator,
but does not actually implement it.
<LI> You have a Kerberos-capable version of <EM>Alpine</EM> and the server is
also Kerberos-capable, but you can not obtain Kerberos
credentials on the server machine, thus you desire to disable
GSSAPI (which in turn disables <EM>Alpine</EM>'s Kerberos support).
</OL>

<P>
It is never necessary to disable authenticators, since <EM>Alpine</EM> will try
other authenticators before giving up.
However, disabling the relevant authenticator avoids annoying error messages.
<P>

<DT> <A NAME="disable-these-drivers"><EM>disable-these-drivers</EM></A>

<DD> This variable is a list of mail drivers which will be disabled.
The candidates for disabling are listed below.
There may be more in the future if you compile <EM>Alpine</EM> with
a newer version of the c-client library.
<P>

<UL>
<LI> mbox
<LI> mbx
<LI> mh
<LI> mix
<LI> mmdf
<LI> mtx
<LI> mx
<LI> news
<LI> phile
<LI> tenex
<LI> unix
</UL>
<P>

The <EM>mbox</EM> driver enables the following behavior: if there is a
file called <CODE>mbox</CODE>
in your home directory, and if that file is either empty or in Unix mailbox
format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver
will automatically transfer mail from the system mail spool directory into the
<CODE>mbox</CODE> file and
delete it from the spool directory. If you disable the <EM>mbox</EM> driver,
this will not happen.
<P>

It is not recommended to disable the driver which supports the system default
mailbox format. On most non-SCO systems, that driver is the
<EM>unix</EM> driver.
On most SCO systems, it is the <EM>mmdf</EM> driver.
The system default driver may be
configured to something else on your system; check with your system manager
for additional information.
<P>

It is most likely not very useful for you to disable any of the drivers other
than possibly <EM>mbox</EM>.
You could disable some of the others if you know for
certain that you don't need them but the performance gain in doing so
is very modest.
<P>

<DT> <A NAME="disp-char-set"><EM>display-character-set</EM></A>

<DD> See the discussion in
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for
details.<P>

<DT> <A NAME="display-filters"><EM>display-filters</EM></A>

<DD> This option defines a list of text-filtering commands (programs or
scripts) that may be used to filter text portions of received messages
prior to their use (e.g., presentation in the "Message Text" display
screen).  For security reasons, the full path name of the filter command
must be specified.
<P>
Display filters do not work with <EM>PC-Alpine</EM>.
<P>

The command is executed and the message is piped into its standard input. 
The standard output of the command is read back by <EM>Alpine</EM>.  The
<EM>_TMPFILE_</EM> token (see below) overrides this default behavior. 

<P> 
The filter's use is based on the configured <EM>trigger</EM> string.  The
format of a filter definition is:

<P>   
<CENTER>&lt;trigger&gt; &lt;command&gt; &lt;arguments&gt;</CENTER>

<P>
You can specify as many filters as you wish, separating them with a comma.  
Each filter can have only one trigger and command.  Thus, two trigger 
strings which invoke the same command require separate filter 
specifications. 

<P> 
The <EM>trigger</EM> is simply text that, if found in the message,
will invoke the associated command.  If the trigger contains any space
characters, it must be placed within quotes.  Likewise, should you
wish a filter to be invoked unconditionally, define the trigger as the
null string, &quot;&quot; (two consecutive double-quote characters).  If the
trigger string is found anywhere in the text of the message the filter
is invoked.  Placing the trigger text within the tokens defined below
changes where within the text the trigger must be before considering
it a match.

<P>  
Trigger Modifying Tokens:
<DL>
<DT><EM>_CHARSET(<VAR>string</VAR>)_</EM>
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command
if the text is in a character set matching <VAR>string</VAR>
(e.g., ISO-8859-2 or ISO-2022-JP).

<DT><EM>_LEADING(<VAR>string</VAR>)_</EM>
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command
if the enclosed <VAR>string</VAR> is found to be the first
non-whitespace text.
<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
the space character.

<DT><EM>_BEGINNING(<VAR>string</VAR>)_</EM>
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command
if the enclosed <VAR>string</VAR> is found at the beginning
of any line in the text.
<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
the space character.
</DL>

<P>
The &quot;command&quot; and &quot;arguments&quot; portion is simply
the command line to be invoked if the trigger string is found.  Below
are tokens that <EM>Alpine</EM> will recognize and replace with special values
when the command is actually invoked.

<P>
Command Modifying Tokens:

<DL>
<DT><EM>_TMPFILE_</EM>
<DD>When the command is executed, this token is 
replaced with the path and name of the temporary 
file containing the text to be filtered.  <EM>Alpine</EM> 
expects the filter to replace this data with the 
filter's result.

NOTE: Use of this token implies that the text to 
be filtered is not piped into standard input of the 
executed command and its standard output is ignored. 
<EM>Alpine</EM> restores the tty modes before invoking the
filter in case the filter interacts with the user
via its own standard input and output.  
                        
<DT><EM>_RESULTFILE_</EM>
<DD>When the command is executed, this token is 
replaced with the path and name of a temporary 
file intended to contain a status message from the 
filter.  <EM>Alpine</EM> displays this in the message status 
field. 
 
<DT><EM>_DATAFILE_</EM>
<DD>When the command is executed, this token is 
replaced with the path and name of a temporary 
file that <EM>Alpine</EM> creates once per session and deletes 
upon exit.  The file is intended to be used by the 
filter to store state information between instances 
of the filter.
   
<DT><EM>_PREPENDKEY_</EM>
<DD>When the command is executed, this token indicates that a random
number will be passed down the input stream before the message text.
This number could be used as a session key.
It does not appear as a command-line argument.
It is sent in this way to improve security.
The number is unique to the current <EM>Alpine</EM> session
and is only generated once per session.
</DL>

<P>
The feature
<A HREF="#disable-terminal-reset-for-display-filters"><EM>disable-terminal-reset-for-display-filters</EM></A> is related.
<P>
Performance caveat/considerations:
<BR>
Testing for the trigger and invoking the filter doesn't come for free.
There is overhead associated with searching for the trigger string, testing
for the filter's existence and actually piping the text through the filter.
The impact can be reduced if the Trigger Modifying Tokens above are 
employed.
<P>
Limitation:
<BR>
If Header Colors are being used, the sequences of bytes which indicate
color changes will be contained in the text which is passed to the
display-filter.
If this causes problems you'll need to turn off Header Colors.
The thirteen bytes which indicate a color change are
the character \377 followed by
\010 for a foreground color or \011 for a background color.
Then comes eleven characters of RGB data which looks something like
255,&nbsp;&nbsp;0,255, depending on the particular color, of course.
<P>

<DT> <A NAME="download-command"><EM>download-command</EM></A>

<DD> This option affects the behavior of the <EM>Export</EM> command.
It specifies a Unix program name, and any necessary command line arguments,
that <EM>Alpine</EM> can use to transfer the exported message to your
personal computer's disk.
<P>

<DT> <A NAME="download-command-prefix"><EM>download-command-prefix</EM></A>

<DD> This option is used in conjunction with the <EM>download-command</EM>
option. 
It defines text to be written to the terminal emulator (via standard
output) immediately prior to starting the download command. This is
useful for integrated serial line file transfer agents that permit command
passing (e.g., Kermit's APC method). <P>
 
<DT> <A NAME="editor"><EM>editor</EM></A>

<DD> UNIX <EM>Alpine</EM> only.  Sets the name of the alternate editor for composing
mail (message text only, not headers).  It will be invoked with the "^_"
command or it will be invoked automatically if the
<A HREF="#enable-alt-imp"><EM>enable-alternate-editor-implicitly</EM></A>
feature is set.  <P>

<DT> <A NAME="empty-header-message"><EM>empty-header-message</EM></A>

<DD> When sending, if both the To and Cc fields are empty and you
are sending the message to a Bcc,
<EM>Alpine</EM> will put a special address in the To line. The default value is
"undisclosed-recipients: ;". The reason for this is to avoid
embarrassment caused by some Internet mail transfer software that
interprets a "missing" To: header as an error and replaces it with an
Apparently-to: header that may contain the addresses you entered on the
Bcc: line, defeating the purpose of the Bcc. You may change the part
of this message that comes before the ": ;" by setting the
<EM>empty-header-message</EM> variable to something else.
<P>

<DT> <A NAME="fcc-name-rule"><EM>fcc-name-rule</EM></A>

<DD> Determines default folder name for fcc when composing.  Currently,
<EM>Alpine</EM> will accept the values <EM>default-fcc</EM>, <EM>by-recipient</EM>,
or <EM>last-fcc-used</EM>.  If set to <EM>default-fcc</EM>, then <EM>Alpine</EM> will
use the value defined in the <A HREF="#def-fcc"><EM>default-fcc</EM></A>
variable (which itself
has a default) for the Fcc header field.  If set to <EM>by-recipient</EM>,
then <EM>Alpine</EM> will use the name of the recipient as a folder name for the fcc. 
The relevant recipient is the first address in the To field.  If set to
"last-fcc-used", then <EM>Alpine</EM> will offer to Fcc to whatever folder
you used previously.
In all cases, the field can still be edited after it is
initially assigned.  If the fcc field in the address book is set for the
first To address, that value over-rides any value derived from this rule. 
<P>

<DT> <A NAME="feat-list"><EM>feature-list</EM></A>

<DD> This is a list of the many features (options) which may be turned on
or off. There is a separate section titled 
<A HREF="#features-conf">Configuration Features</A> which explains
each of the features. There is some additional explanation about the
<EM>feature-list</EM> variable itself
in <A HREF="config-notes.html#feature-list"><EM>Feature List Variable</EM></A>.
<P>

<DT> <A NAME="file-directory"><EM>file-directory</EM></A>

<DD> <EM>PC-Alpine</EM> only.
This value affects the Composer's &quot;^J Attach&quot; command, 
the Attachment Index Screen's &quot;S Save&quot; command, and the
Message Index's &quot;E Export&quot; command.

<P>
Normally, when a filename is supplied that lacks a leading &quot;path&quot;
component, <EM>Alpine</EM> assumes the file exists in the user's home directory.
Under Windows operating systems, this definition isn't always clear.  This 
feature allows you to explicitly set where <EM>Alpine</EM> should look for files
without a leading path.

<P>
NOTE: this feature's value is ignored if either 
<A HREF="#use-current-dir"><EM>use-current-dir</EM></A> feature
is set or the PINERC has a value for the
<A HREF="#operating-dir"><EM>operating-dir</EM></A> variable.
<P>

<DT> <A NAME="fold-coll"><EM>folder-collections</EM></A>

<DD> This is a list of one or more collections where saved mail is stored. 
See the sections describing
<A HREF="config-notes.html#collections">folder collections and collection syntax</A> for more information.
The first collection in this list is the default
collection for <EM>Save</EM>s,
including <A HREF="#def-fcc"><EM>default-fcc</EM>'s</A>.
<P>

<DT> <A NAME="folder-ext"><EM>folder-extension</EM></A>

<DD> <EM>PC-Alpine</EM> only. File extension used for local folder names. This
is <CODE>.MTX</CODE> by default.
<P>

<DT> <A NAME="reopen-rule"><EM>folder-reopen-rule</EM></A>

<DD> <EM>Alpine</EM> normally checks for new mail in the currently open folder
and in the INBOX every few <A HREF="#mail-check"><EM>minutes</EM></A>.

<P>
There are some situations where automatic new-mail checking does not work.
For example, if a mail folder is opened using the POP protocol or a newsgroup
is being read using the NNTP protocol, then new-mail checking is disabled.

<P>
It may be possible to check for new mail in these cases by reopening the
folder.
<EM>Alpine</EM> does not do this for you automatically, but you may do the commands
manually to cause this to happen.
You reopen by going back to the folder list screen from the message
index screen with the &quot;&lt;&quot; command,
and then going back into the message index screen with
the &quot;&gt;&quot; command.
(Actually, any method you would normally use to open a folder will work the
same as the &quot;&lt;&quot; followed by &quot;&gt;&quot; method.
For example, the GoTo Folder command will work, or you may use L to go to the
Folder List screen and Carriage Return to reopen the folder.)

<P>
There are some cases where <EM>Alpine</EM> knows that reopening the folder should
be useful as a way to discover new mail.
At the time of this writing, connections made using the POP protocol,
news reading using the NNTP protocol, local news reading, and local
ReadOnly folders which are in the traditional UNIX or the MMDF format all
fall into this category.
There are other cases where it <EM>may</EM> be a way to discover new mail, but <EM>Alpine</EM>
has no way of knowing, so it might also just be an exercise in futility.
All remote, ReadOnly folders other than those listed just above fall into this
category.
The setting of this option together with the type of folder
controls how <EM>Alpine</EM> will react to the apparent attempt to reopen a folder.

<P>
If you don't reopen, then you will just be back in
the message index with no change.
You left the index and came back, but the folder remained &quot;open&quot;
the whole time.
However, if you do reopen the folder, the folder is closed and then reopened.
In this case, the current state of the open folder is lost.
The New status, Important and Answered flags,
selected state, Zoom state, collapsed or expanded state of threads,
current message number,
and any other temporary state is all lost when the reopen happens.
For POP folders (but not NNTP newsgroups) the Deleted flags are also lost.

<P>
In the possibilities listed below, the text says &quot;POP/NNTP&quot; in
several places.
That really implies the case where <EM>Alpine</EM> knows it is a good way to discover
new mail, which is more than just POP and NNTP, but POP and NNTP are
the cases of most interest.
This option probably has more possible values than it deserves. They are:
<P>

<DL>
<DT>Always reopen</DT>
<DD><EM>Alpine</EM> will not ask whether you want to reopen but will just do the reopen
whenever you type a command that implies a reopen, regardless of the
access method.
In other words, it is assumed you would always answer Yes if asked
about reopening.
</DD>

<DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT>
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, but
will ask you whether to reopen other remote folders,
with a default answer of Yes.
</DD>

<DT>Yes for POP/NNTP, Ask about other remote [No]</DT>
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, but
will ask you whether to reopen other remote folders,
with a default answer of No.
</DD>

<DT>Yes for POP/NNTP, No for other remote</DT>
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, and
will assume a No answer for all other remote folders.
</DD>

<DT>Always ask [Yes]</DT>
<DD><EM>Alpine</EM> will not differentiate based on access method.
It will always ask for all remote folders, with a default answer of Yes.
</DD>

<DT>Always ask [No]</DT>
<DD><EM>Alpine</EM> will not differentiate based on access method.
It will always ask for all remote folders, with a default answer of No.
</DD>

<DT>Ask about POP/NNTP [Yes], No for other remote</DT>
<DD><EM>Alpine</EM> will ask if the access method is POP or NNTP, with a default answer
of Yes.
It will never attempt to reopen other remote folders.
</DD>

<DT>Ask about POP/NNTP [No], No for other remote</DT>
<DD>This is the default.
<EM>Alpine</EM> will ask if the access method is POP or NNTP, with a default answer
of No.
It will never attempt to reopen other remote folders.
</DD>

<DT>Never reopen</DT>
<DD><EM>Alpine</EM> will never attempt to reopen already open folders.
</DD>
</DL>

<P>
Remember, wherever it says POP or NNTP above it really means POP or NNTP or
any of the other situations where it is likely that reopening is a good way
to discover new mail.

<P>
There is an alternative that may be of useful in some situations.
Instead of manually checking for new mail you can set up a
<A HREF="config-notes.html#maildrop">Mail Drop</A>
and automatically check for new mail.
<P>

<DT> <A NAME="folder-sort-rule"><EM>folder-sort-rule</EM></A>

<DD> This option controls the order in which folder list entries will be
presented in the FOLDER LIST screen.  Choose one of the following:

 <DL>
 <DT> <EM>Alphabetical</EM>

 <DD> sort by alphabetical name independent of type

 <DT> <EM>Alpha-with-dirs-last</EM>

 <DD> sort by alphabetical name grouping directory entries
to the end of the list

 <DT> <EM>Alpha-with-dirs-first</EM>

 <DD> sort by alphabetical name grouping directory entries
to the start of the list
 </DL>

The normal default is <EM>Alphabetical</EM>.
<P>

<DT> <A NAME="font-name"><EM>font-name</EM></A>

<DD> Winsock version of <EM>PC-Alpine</EM> only.  <P>

<DT> <A NAME="font-size"><EM>font-size</EM></A>

<DD> Winsock version of <EM>PC-Alpine</EM> only.  <P>

<DT> <A NAME="font-style"><EM>font-style</EM></A>

<DD> Winsock version of <EM>PC-Alpine</EM> only.  <P>

<DT> <A NAME="forced-abook"><EM>forced-abook-entry</EM></A>

<DD> System-wide <EM>Alpine</EM> configuration files only.
Force these address book
entries into all writable personal address books.
This is a list variable. Each item in the list has the form:

<BLOCKQUOTE>
   Nickname | Fullname | Address <BR>
</BLOCKQUOTE>

with optional whitespace in all the obvious places.
<P>

<DT> <A NAME="form-letter-folder"><EM>form-letter-folder</EM></A>

<DD> A Form Letter Folder is a mail folder that is intended to
contain messages that you have composed and that are intended to be
sent in their original form repeatedly.

<P>
Setting this variable will alter <EM>Alpine</EM>'s usual behavior when you
execute the Compose command.  Normally, <EM>Alpine</EM> offers a chance to
continue a postponed or interrupted message should one or the other
exist.  When this variable is set to a folder name that exists, <EM>Alpine</EM>
will also offer the chance to select a message from the folder to
insert into the composer, much like when continuing a postponed message.
The difference, however, is that <EM>Alpine</EM> will not automatically delete
the selected message from the Form Letter Folder.
<P>
Setting this variable will also affect <EM>Alpine</EM>'s behavior when you
Postpone a message from the composer.  Normally, <EM>Alpine</EM> simply stashes
the message away in your
<A HREF="#postponed-folder"><EM>Postponed-Folder</EM></A>.
Regardless of the specified folder's existence, <EM>Alpine</EM> will ask which
folder you intend the message to be stored in.  Choose the
&quot;F&quot; option to store the message in your Form Letter Folder.
This is the most common way to add a message to the folder.

<P>
Another method of adding messages to the folder is via the <EM>Alpine</EM>
composer's <SAMP>Fcc:</SAMP> field.  If you are sending a message that
you expect to send in the same form again, you can enter the Form
Letter Folder's name in this field.  <EM>Alpine</EM>, as usual, will copy the
message as it's sent.  Note, when you later select this message from 
your Form Letter Folder, it will have the same recipients as the original
message.

<P>
To delete a message from the Form Letter Folder, you can either select
the folder from a suitable FOLDER LIST screen, or use the Delete
command in the MESSAGE INDEX offered when selecting from the folder as
part of the Compose command.  You can delete a Form Letter Folder just
as any other folder from a suitable FOLDER LIST screen.

<P>
You may find that the <A HREF="#role-config"><EM>Roles</EM></A>
facility can be used
to replace the Form Letter Folder.

<P>

<DT> <A NAME="glob-abook"><EM>global-address-book</EM></A>

<DD> A list of shared address books.  Each entry in the list is an
optional nickname followed by a pathname or file name relative to the home
directory.
A SPACE character separates the nickname from the rest of the line.
Instead of a local pathname or file name, a remote folder name can be given.
This causes the address book to
be a <A HREF="low-level.html#addrbook"><EM>Remote address book</EM></A>.
Remote folder syntax is discussed in
<A HREF="config-notes.html#remote-folders">Syntax for Remote Folders</A>.
This list will be added to the
<A HREF="#pers-abook"><EM>address-book</EM></A> list to
arrive at the complete set of address books.  Global address books are
defined to be ReadOnly.  <P>

<DT> <A NAME="goto-default-rule"><EM>goto-default-rule</EM></A>

<DD> This value affects <EM>Alpine</EM>'s behavior when using
the <EM>Goto</EM> command.
There are five possible values for this option:
<P>

 <DL>

 <DT> <EM>folder-in-first-collection</EM>

 <DD> <EM>Alpine</EM> will offer the most recently visited folder in the default
collection found in the &quot;Collection List&quot; screen as the default.
<P>
 
 <DT> <EM>inbox-or-folder-in-first-collection</EM>

 <DD> If the current folder is <EM>INBOX</EM>,
<EM>Alpine</EM> will offer the most recently visited folder in the
default collection found in the &quot;Collection List&quot; screen.
If the current folder is other than <EM>INBOX</EM>,
<EM>INBOX</EM> is offered as the default.
<P>
 
 <DT> <EM>inbox-or-folder-in-recent-collection</EM>

 <DD> This is <EM>Alpine</EM>'s default behavior.
If the current folder is <EM>INBOX</EM>,
<EM>Alpine</EM> will offer the last open
folder as the default.
If the current folder is other than <EM>INBOX</EM>,
<EM>INBOX</EM> is offered as the default.
<P>
 
 <DT> <EM>first-collection-with-inbox-default</EM>

 <DD> Instead of offering the most recently visited folder in the default
collection, the default collection is offered but with <EM>INBOX</EM> as
the default folder.
If you type in a folder name it will be in the default collection.
If you simply accept the default, however, your <EM>INBOX</EM> will be opened.
<P>

 <DT> <EM>most-recent-folder</EM>

 <DD> The last accepted value simply causes the most recently opened
folder to be offered as the default regardless of the currently opened
folder.
<P>
 
 </DL>
 
NOTE: The default while a newsgroup is open remains the same; the last
open newsgroup. <P>

<DT> <A NAME="header-general-background-color"><EM>header-general-background-color</EM></A>
<DT> <A NAME="header-general-foreground-color"><EM>header-general-foreground-color</EM></A>

<DD> <A HREF="#header-colors"><EM>Header Colors</EM></A>.
<P>

<DT> <A NAME="image-viewer"><EM>image-viewer</EM></A>

<DD> This variable names the program to call for displaying parts of a
MIME message that are of type IMAGE.  If your system supports the
<EM>mailcap</EM> system, you don't need to set this variable.  <P>

<DT> <A NAME="inbox-path"><EM>inbox-path</EM></A>

<DD> This specifies the name of the folder to use for the <EM>INBOX</EM>.
By default this is unset and the system's default is used.
The most common reason for
setting this is to open an IMAP mailbox for the <EM>INBOX</EM>.  For example,
<EM>{imap5.u.example.edu}inbox</EM> will open the user's standard
<EM>INBOX</EM> on the mail server, <EM>imap5</EM>.  <P>

<DT> <A NAME="incoming-archive-folders"><EM>incoming-archive-folders</EM></A>

<DD> This is like <A HREF="#read-msg-fold"><EM>read-message-folder</EM></A>,
only more general. This is a list
of folder pairs, with the first separated from the second in the pair by a
space.  The first folder in a pair is the folder you want to archive, and
the second folder is the folder that read messages from the first should
be moved to.  Depending on how you define the
<A HREF="#auto-read-msg"><EM>auto-move-read-msgs</EM></A>
feature, you may or may not be asked when you leave
the first folder if you want read messages to be moved to the second
folder. In either case, moving the messages means they will be deleted
from the first folder. <P>
 
If these are not path names, they will be in the default collection for
<EM>Save</EM>s.  Any valid folder specification, local or remote (via IMAP), is
allowed.  There is no default. <P>

<DT> <A NAME="incoming-check-interval"><EM>incoming-check-interval</EM></A>

<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
This option specifies, in seconds, how often <EM>Alpine</EM> will check
for new mail and state changes in Incoming Folders when Incoming Folders
Checking is turned on.
The default is 3 minutes (180).
This value applies only to folders that are local to the system that
<EM>Alpine</EM> is running on or that are accessed using the IMAP protocol.
The similar option
<A HREF="#incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A>
applies to all other monitored folders.
<P>

<DT> <A NAME="incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A>

<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
This option together with the option
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A>
specifies, in seconds, how often <EM>Alpine</EM> will check
for new mail and state changes in Incoming Folders when Incoming Folders
Checking is turned on.
The default for this option is 3 minutes (180).
For folders that are local to this system or
that are accessed using the IMAP protocol
the value of the option
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A>
is used.
For all other monitored folders, the value of this option is used.
<P>
The reason there are two separate options is because it is usually
less expensive to check local and IMAP folders than it is to check
other types, like POP or NNTP folders.
You may want to set this secondary value to a higher number than
the primary check interval.
<P>

<DT> <A NAME="incoming-check-list"><EM>incoming-check-list</EM></A>

<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
When monitoring the Incoming Message Folders for Unseen messages Alpine will
normally monitor all Incoming Folders.
You may use this option to restrict the list of monitored folders to a
subset of all Incoming Folders.
<P>

<DT> <A NAME="incoming-check-timeout"><EM>incoming-check-timeout</EM></A>

<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
Sets the time in seconds that Alpine will
attempt to open a network connection used for monitoring for Unseen
messages in Incoming Folders. The default is 5.
If a connection has not completed within this many seconds Alpine will
give up and consider it a failed connection.
<P>

<DT> <A NAME="inc-fold"><EM>incoming-folders</EM></A>

<DD> This is a list of one or more folders other than <EM>INBOX</EM> that
may receive new messages.  This list is slightly special in that it is
always expanded in the folder lister.  In the future, it may become more
special.  For example, it would be nice
if <EM>Alpine</EM> would monitor the folders
in this list for new mail.  <P>

<DT> <A NAME="incoming-startup-rule"><EM>incoming-startup-rule</EM></A>

<DD> This rule affects <EM>Alpine</EM>'s behavior when opening
the <EM>INBOX</EM> or
another folder from the "INCOMING MESSAGE FOLDERS".
This rule tells <EM>Alpine</EM>
which message to make the current message when an incoming folder is opened.
There are seven possible values for this option:
<P>

 <DL>

 <DT> <EM>first-unseen</EM>

 <DD> The current message will be the first unseen message which has not been
marked deleted, or the last message if all of the messages have been seen.
This is the default setting.
<P>
 
 <DT> <EM>first-recent</EM>

 <DD> This is similar to <EM>first-unseen</EM>. Instead of first unseen
it is the first recent message. A message is considered to be recent if it
arrived since the last time the folder was open (by any mail client, not just
the current one). So this option causes the
current message to be set to the first undeleted-recent message, or the
last message if none is both undeleted and recent.
<P>

 <DT> <EM>first-important</EM>

 <DD> This will result in the current message being set to the first
message marked Important (but not Deleted).
If no messages are marked Important, then it will be the last message.
<P>

 <DT> <EM>first-important-or-unseen</EM>

 <DD> This selects the minimum of the first unseen and the first important
messages.
<P>

 <DT> <EM>first-important-or-recent</EM>

 <DD> This selects the first of the first recent and the first important
messages.
<P>

 <DT> <EM>first</EM>

 <DD> Set the current message to the first undeleted message unless all
are deleted. In that case set it to the last message.
<P>
 
 <DT> <EM>last</EM>

 <DD> Set the current message to the last undeleted message unless all
are deleted. In that case set it to the last message.
<P>
 
 </DL>
<P>

<DT> <A NAME="incoming-unseen-background-color"><EM>incoming-unseen-background-color</EM></A>
<DT> <A NAME="incoming-unseen-foreground-color"><EM>incoming-unseen-foreground-color</EM></A>

<DD> <A HREF="#incoming-unseen-color"><EM>Incoming Unseen Color</EM></A>.
<P>

<DT> <A NAME="index-answered-background-color"><EM>index-answered-background-color</EM></A>
<DT> <A NAME="index-answered-foreground-color"><EM>index-answered-foreground-color</EM></A>
<DT> <A NAME="index-arrow-background-color"><EM>index-arrow-background-color</EM></A>
<DT> <A NAME="index-arrow-foreground-color"><EM>index-arrow-foreground-color</EM></A>
<DT> <A NAME="index-deleted-background-color"><EM>index-deleted-background-color</EM></A>
<DT> <A NAME="index-deleted-foreground-color"><EM>index-deleted-foreground-color</EM></A>
<DT> <A NAME="index-from-background-color"><EM>index-from-background-color</EM></A>
<DT> <A NAME="index-from-foreground-color"><EM>index-from-foreground-color</EM></A>
<DT> <A NAME="index-highpriority-background-color"><EM>index-highpriority-background-color</EM></A>
<DT> <A NAME="index-highpriority-foreground-color"><EM>index-highpriority-foreground-color</EM></A>
<DT> <A NAME="index-important-background-color"><EM>index-important-background-color</EM></A>
<DT> <A NAME="index-important-foreground-color"><EM>index-important-foreground-color</EM></A>
<DT> <A NAME="index-lowpriority-background-color"><EM>index-lowpriority-background-color</EM></A>
<DT> <A NAME="index-lowpriority-foreground-color"><EM>index-lowpriority-foreground-color</EM></A>
<DT> <A NAME="index-new-background-color"><EM>index-new-background-color</EM></A>
<DT> <A NAME="index-new-foreground-color"><EM>index-new-foreground-color</EM></A>
<DT> <A NAME="index-opening-background-color"><EM>index-opening-background-color</EM></A>
<DT> <A NAME="index-opening-foreground-color"><EM>index-opening-foreground-color</EM></A>
<DT> <A NAME="index-recent-background-color"><EM>index-recent-background-color</EM></A>
<DT> <A NAME="index-recent-foreground-color"><EM>index-recent-foreground-color</EM></A>
<DT> <A NAME="index-subject-background-color"><EM>index-subject-background-color</EM></A>
<DT> <A NAME="index-subject-foreground-color"><EM>index-subject-foreground-color</EM></A>
<DT> <A NAME="index-to-me-background-color"><EM>index-to-me-background-color</EM></A>
<DT> <A NAME="index-to-me-foreground-color"><EM>index-to-me-foreground-color</EM></A>
<DT> <A NAME="index-unseen-background-color"><EM>index-unseen-background-color</EM></A>
<DT> <A NAME="index-unseen-foreground-color"><EM>index-unseen-foreground-color</EM></A>

<DD> <A HREF="#index-colors"><EM>Index Colors</EM></A>.
<P>

<DT> <A NAME="index-format"><EM>index-format</EM></A>

<DD> This option is used to customize the content of lines in the
MESSAGE INDEX screen.  Each line is intended 
to convey some amount of immediately relevant information about each 
message in the current folder.
<P>

<EM>Alpine</EM> provides a pre-defined set of informational fields with
reasonable column widths automatically computed.  You can, however,
replace this default set by listing special tokens in the order you
want them displayed.
<P>

The list of available tokens is
<A HREF="#index-tokens"><EM>here</EM></A>.
<P>

Spaces are used to separate listed tokens.  Additionally, you can
specify how much of the screen's width the taken's associated data
should occupy on the index line by appending the token with a pair of
parentheses enclosing either a number or percentage.  For example,
&quot;SUBJECT(13)&quot; means to allocate 13 characters of space to the subject
column, and &quot;SUBJECT(20%)&quot; means to
allocate 20% of the available space
to the subjects column, while plain &quot;SUBJECT&quot; means the system will
attempt to figure out a reasonable amount of space.
<P>

There is always one space between every pair of columns, so if you use fixed
column widths (like 13) you should remember to take that into account.
Several of the fields are virtually fixed-width, so it doesn't make
much sense to specify the width for them.  The fields STATUS,
FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE,
and DESCRIPSIZE all fall into that category.
You <EM>may</EM> specify widths for those if you wish, but
you're probably better off letting the system pick those widths.  <P>

<P>
The default is equivalent to:

<P>
<CENTER><SAMP>index-format=STATUS&nbsp;MSGNO&nbsp;SMARTDATETIME24&nbsp;FROMORTO(33%)&nbsp;SIZENARROW&nbsp;SUBJKEY(67%)</SAMP></CENTER>

<P>
This means that the four fields without percentages will be allocated
first, and then 33% and 67% of the <EM>remaining</EM> space will go to
the from and subject fields.  If one of those two fields is specified
as a percentage and the other is left for the system to choose, then
the percentage is taken as an absolute percentage of the screen, not
of the space remaining after allocating the first four columns.  It
doesn't usually make sense to do it that way.  If you leave off all
the widths, then the subject and from fields (if both are present) are
allocated space in a 2 to 1 ratio, which is almost exactly the same as
the default.

<P>
What you are most likely to do with this configuration option is to
specify which fields appear at all, which order they appear in, and the
percentage of screen that is used for the from and subject fields if you
don't like the 2 to 1 default.
<P>
If you want to retain the default format that <EM>Pine</EM> 4.64 had, use

<P>
<CENTER><SAMP>Index-Format=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER>
<P>

<EM>and</EM> set the feature
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A>.

<P>

<DT> <A NAME="initial-keystroke-list"><EM>initial-keystroke-list</EM></A>

<DD> This is a comma-separated list of keystrokes which <EM>Alpine</EM> executes on
startup.  Items in the list are usually just characters, but there are
some special values.  <EM>SPACE,</EM> <EM>TAB,</EM> and <EM>CR</EM> mean a
space character, tab character, and a carriage return, respectively. 
<EM>F1</EM> through <EM>F12</EM> stand for the twelve function keys. 
<EM>UP, DOWN, LEFT, </EM>and<EM> RIGHT </EM>stand for the arrow keys. 
Control characters are represented with <EM>^&lt;char&gt;</EM>.  A
restriction is that you can't mix function keys and character keys in this
list even though you can, in some cases, mix them when running <EM>Alpine</EM>.  A
user can always use only <EM>character</EM> keys in the startup list even
if he or she is using <EM>function</EM> keys normally, or vice versa. If
an element in this list is a string surrounded by double quotes (")
then it will be expanded into the individual characters in the string,
excluding the double quotes. <P>

<DT> <A NAME="kblock-count"><EM>kblock-passwd-count</EM></A>

<DD> System-wide <EM>Alpine</EM> configuration files only. Number of times a user
will have to enter a password when they run the keyboard lock command in
the main menu. <P>

<DT> <A NAME="keyb-char-set"><EM>keyboard-character-set</EM></A>

<DD> See the discussion in
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for
details.<P>

<DT> <A NAME="keylabel-background-color"><EM>keylabel-background-color</EM></A>
<DT> <A NAME="keylabel-foreground-color"><EM>keylabel-foreground-color</EM></A>

<DD> <A HREF="#keylabel-color"><EM>KeyLabel Color</EM></A>.
<P>

<DT> <A NAME="keyname-background-color"><EM>keyname-background-color</EM></A>
<DT> <A NAME="keyname-foreground-color"><EM>keyname-foreground-color</EM></A>

<DD> <A HREF="#keyname-color"><EM>KeyName Color</EM></A>.
<P>

<DT> <A NAME="keywords"><EM>keywords</EM></A>

<DD> You may define your own set of keywords and optionally set them on a
message by message basis.
These are similar to the &quot;Important&quot; flag which the user
may set using the Flag command.
The difference is that the Important flag is always present for each folder.
User-defined keywords are chosen by the user.
You may set up the list of possible keywords here, or you may add keywords
from the Flag Details screen that you
can get to after typing the
Flag (*)
command.
After the keywords have been defined,
then you use the Flag command
to set or clear the keywords in each message.
The behavior of the flag command may be modified by using the
<A HREF="#enable-flag-screen-implicitly">Enable-Flag-Screen-Implicitly</A> option or the
<A HREF="#enable-flag-screen-keyword-shortcut"><EM>Enable-Flag-Screen-Keyword-Shortcut</EM></A> option.

<P>
Keywords may be used when Selecting messages (Select Keyword).
Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc).
Filter rules may be used to set keywords automatically.
Keywords may be displayed as part of the Subject of a message by using
the SUBJKEY or SUBJKEYINIT tokens in the
<A HREF="#index-format">Index-Format</A> option.
The <A HREF="#keyword-surrounding-chars"><EM>Keyword-Surrounding-Chars</EM></A>
option may be used to modify the display of keywords using
SUBJKEY and SUBJKEYINIT slightly.
Keywords may also be displayed in a column of their own in the MESSAGE INDEX
screen by using the KEY or KEYINIT tokens.
It is also possible to color keywords in the index using the
Setup/Kolor screen
(<A HREF="#keyword-colors">Keyword Colors</A>).
Keywords are not supported by all mail servers.
<P>
You may give keywords nicknames if you wish.
If the keyword definition you type in contains a SPACE character, then the
actual value of the keyword is everything after the last SPACE and the
nickname for that keyword is everything before the last SPACE.
For example, suppose you are trying to interoperate with another email program
which uses a particular keyword with an unpleasant name.
Maybe it uses a keyword called
<P>
<CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER>
<P>
but for you that keyword means that the message is work-related.
You could define a keyword to have the value
<P>
<CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER>
<P>
and then you would use the name &quot;Work&quot; when dealing with
that keyword in <EM>Alpine</EM>.
If you defined it as
<P>
<CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER>
<P>
the nickname would be everything before the last SPACE, that is the nickname
would be &quot;My Work&quot;.
<P>
Some commonly used keywords begin with dollar signs.
This presents a slight complication, because the dollar sign is normally used
to signify
<A HREF="config-notes.html#env-variables">environment variable expansion</A>
in the <EM>Alpine</EM> configuration.
In order to specify a keyword which begins with a dollar sign you must
precede the dollar sign with a second dollar sign to escape its special
meaning.
For example, if you want to include the keyword
<P>
<CENTER><SAMP>$Label1</SAMP></CENTER>
<P>
as one of your possible keywords, you must enter the text
<P>
<CENTER><SAMP>$$Label1</SAMP></CENTER>
<P>
instead.
<P>

<DT> <A NAME="keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A>

<DD> This option controls a minor aspect of <EM>Alpine</EM>'s MESSAGE INDEX and MESSAGE
TEXT screens.
If you have modified the
<A HREF="#index-format"><EM>Index-Format</EM></A> option
so that either the &quot;SUBJKEY&quot; or &quot;SUBJKEYINIT&quot; tokens
are used to display keywords or their initials along with the Subject; then
this option may be used to modify the resulting display slightly.
By default, the keywords or initials displayed for these tokens will be
surrounded with curly braces ({ and }) and a trailing space.
For example, if keywords &quot;Work&quot; and &quot;Now&quot; are set for
a message, the &quot;SUBJKEY&quot; token will normally look like
<P>
<CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
<P>
and the SUBJKEYINIT token would look like
<P>
<CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
<P>
The default character before the keywords is the left brace ({) and the
default after the keywords is the right brace followed by a space (} ).
<P>
This option allows you to change that.
You should set it to two values separated by a space.
The values may be quoted if they include space characters.
So, for example, the default value could be specified explicitly by setting this
option to
<P>
<CENTER><SAMP>Keyword-Surrounding-Chars="{" "} "</SAMP></CENTER>
<P>
The first part wouldn't need to be quoted (but it doesn't hurt).
The second part does need the quotes because it includes a space character.
If you wanted to change the braces to brackets you could use
<P>
<CENTER><SAMP>Keyword-Surrounding-Chars="[" "] "</SAMP></CENTER>
<P>
Inside the quotes you can use backslash quote to mean quote, so
<P>
<CENTER><SAMP>Keyword-Surrounding-Chars="&#92;"" "&#92;" "</SAMP></CENTER>
<P>
would produce
<P>
<CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER>
<P>
It is also possible to color keywords in the index using the
Setup/Kolor screen
(<A HREF="#keyword-colors">Keyword Colors</A>).
<P>
It is not possible to change the fact that a space character is used to
separate the keywords if more than one keyword is set for a message.
It is also not possible to change the fact that there are no separators
between the keyword initials if more than one keyword is set.
<P>
This option is displayed as &quot;Keyword Surrounding Characters&quot;.
<P>

<DT> <A NAME="last-time"><EM>last-time-prune-questioned</EM></A>

<DD> Personal configuration file only.  This variable records the month
the user was last asked if his or her <EM>sent-mail</EM> folders should
be pruned. 
The format is <EM>yy.mm</EM>.
This is automatically updated by <EM>Alpine</EM> when
the the pruning is done or declined.
If a user wanted to make <EM>Alpine</EM> stop
asking this question he or she could set this time to something
far in the future.
This may not be set in the system-wide configuration files.
Note: The <EM>yy</EM> year is actually the number of years since 1900, so it
will be equal to 101 in the year 2001.
<P>

<DT> <A NAME="last-version-used"><EM>last-version-used</EM></A>

<DD> Personal configuration file only.
This is set automatically by <EM>Alpine</EM>. 
It is used to keep track of the last version of <EM>Alpine</EM> that
was run by the user.
Whenever the version number increases, a new version message is printed out.
This may not be set in the system-wide configuration files.
<P>

<DT> <A NAME="ldap-servers"><EM>ldap-servers</EM></A>

<DD> This is only available if <EM>Alpine</EM> was linked with an LDAP library
when it was compiled. This variable is normally managed by <EM>Alpine</EM> though
it can be set in the system-wide configuration files as well as the personal
configuration. It is a list variable. Each item in the
list contains quite a bit of extra information besides just the server name.
To put this into a system-wide config file the easiest thing to do is to
configure a personal <EM>Alpine</EM> for the LDAP server then copy the
configuration line
into the system-wide config file. Each item in the list looks like:

<BLOCKQUOTE>
     <CODE>
     server_name[:port] <SPACE> "quoted stuff" </CODE><BR>
</BLOCKQUOTE>

The <CODE>server_name</CODE> is just a hostname and it is followed by
an optional colon and port number. The default <CODE>port</CODE> is 389.
Following the server name is a single SPACE character followed by
a bunch of characters inside double quotes. The part inside the quotes is
a set of <EM>tag</EM> = <EM>value</EM> pairs.
Each tag is preceded by a slash (/) and followed
by an equal sign. The value for that tag is the text up to the next slash.
An example of some <CODE>quoted stuff</CODE> is:

<BLOCKQUOTE>
     <CODE>
     "/base=o=University of Washington, c=US/impl=0/.../nick=My Server"
     </CODE><BR>
</BLOCKQUOTE>

This would set the search base for this server to
<CODE>o=University of Washington, c=US</CODE>, set the implicit bit to zero,
and set the nickname for the server to <CODE>My Server</CODE>.
All of the tags correspond directly to items in the Setup/Directory screen
so experiment with that if you want to see what the possible tags and values
are.
<P>

<DT> <A NAME="literal-signature"><EM>literal-signature</EM></A>

<DD> With this option your actual signature, as opposed to
the name of a file containing your signature,
is stored in the <EM>Alpine</EM> configuration file.
If this is defined it takes precedence over the <EM>signature-file</EM> option.
<P>

This is simply a different way to store the signature data.
The signature is stored inside your <EM>Alpine</EM> configuration file
instead of in a separate signature file.
Tokens contained in the signature work the same way they do with the regular
<A HREF="#sig-file">signature-file</A>.
<P>

The Setup/Signature command in <EM>Alpine</EM>'s Main Menu will edit
the <EM>literal-signature</EM> by default.  However, if no
<EM>literal-signature</EM> is defined and the file named in the
<EM>signature-file</EM> option exists, then the latter will be used
instead.  Compose (Reply, Forward, ...) will default to using the
<EM>literal-signature</EM> if defined, otherwise it will use the contents
of the file named in <EM>signature-file</EM>.
<P>

The <EM>Alpine</EM> composer is used to edit the literal-signature.
The result of that edit is first converted to a C-style string before it
is stored in the configuration file.
In particular, the two character sequence &#92;n (backslash followed by
the character &quot;n&quot;) will be used to signify a
line-break in the signature.
You don't have to enter the &#92;n, but it will be visible in the
SETUP CONFIGURATION window after you are done editing the signature.
<P>

<DT> <A NAME="mail-check"><EM>mail-check-interval</EM></A>

<DD> This option specifies, in seconds,
how often <EM>Alpine</EM> will check for new mail.
If set to zero, new-mail checking is disabled.
(You can always manually force a new-mail check by typing ^L (Ctrl-L), which is also
the command to refresh the screen, or by typing the Next command when the
current message is the last message of the folder.)
There is a minimum value for this option, normally 15 seconds.
The default value is normally 150 seconds.
The higher you set this option, the easier it is on the server.
<P>
There are some situations where automatic new-mail checking does not work.
See the discussion about new-mail checking in <A HREF="#reopen-rule"><EM>folder-reopen-rule</EM></A>.
<P>
The new-mail checking will not happen exactly at the frequency that you specify.
For example, <EM>Alpine</EM> may elect to defer a non-INBOX mail check if you
are busy typing.
Or, it may check more frequently than you have specified if that is
thought to be necessary to keep the server from closing the connection
to the folder due to inactivity.
If <EM>Alpine</EM> checks for new mail as a side effect of another command, it will reset
the timer, so that new-mail checking may seem to happen irregularly instead of
every X seconds like clockwork.
<P>
If you are anxious to know about new mail as soon as possible, set the check
interval low, and you'll know about the new mail by approximately
that amount of time after it arrives.
If you aren't so worried about knowing right away, set this option to a
higher value.
That will save the server some processing time and may save you some of
the time you spend waiting for new-mail checks to happen if you are
dealing with a slow server or slow network connection.
<P>
If you suspect that new-mail checking is causing slow downs for you,
you may want to look into the options
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A>,
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A> and
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A>,
which refine when mail checking is done.
<P>
If the mailbox being check uses a <A HREF="config-notes.html#maildrop">Mail Drop</A> then
there is a minimum time
(<A HREF="#maildrop-check-minimum"><EM>maildrop-check-minimum</EM></A>)
between new-mail checks.
Because of this minimum you may notice that new mail does not
appear promptly when you expect it.
The reason for this is to protect the server from over-zealous opening and
closing of the Mail Drop folder, since that is a costly operation.
<P>
A side effect of disabling mail checking is that there will be situations
in which the user's IMAP connection will be broken due to inactivity timers
on the server. Another side effect is that the
<A HREF="#user-input"><EM>user-input-timeout</EM></A>
option won't work.
<P>

<DT> <A NAME="mail-check-noncurr"><EM>mail-check-interval-noncurrent</EM></A>

<DD> This option is closely related to the
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A>
option, as well as the
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A> and
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A> options.
If the &quot;Mail-Check-Interval&quot; option is set to zero, then automatic
new-mail checking is disabled and this option will have no effect.
<P>
Normally this option is set to zero, which means that the value used will be
the same as the value for the &quot;Mail-Check-Interval&quot;.
If you set this option to a value different from zero
(usually larger than the value for &quot;Mail-Check-Interval&quot;)
then that is the check interval that will be used
for folders which are not the currently open folder or the INBOX.
You may not even have any folders that are noncurrent and not the INBOX.
If you do, it is likely that they are due to
<A HREF="#stay-open-folders">Stay-Open-Folders</A>
you have configured.
This option also affects the rate of mail checking done on cached
connections to folders you previously had open but are no longer actively
using.
You aren't expected to understand that last sentence, but if you are interested
take a look at
<A HREF="#max-remote-connections">Max-Remote-Connections</A>,
and the related options.
<P>

<DT> <A NAME="mail-directory"><EM>mail-directory</EM></A>

<DD> This variable was more important in previous versions of <EM>Alpine</EM>.  Now
it is used only as the default for storing personal folders (and only if
there are no <A HREF="#fold-coll"><EM>folder-collections</EM></A> defined).
The default value is
<EM>~/mail</EM> on UNIX and <EM>${HOME}\MAIL</EM> on a PC.  <P>

<DT> <A NAME="mailcap-search-path"><EM>mailcap-search-path</EM></A>

<DD> This variable is used to replace <EM>Alpine</EM>'s default
mailcap file search path.
It takes one or more file names (full paths must be specified) in
which to look for mail capability data.  <P>

<DT> <A NAME="maildrop-check-minimum"><EM>maildrop-check-minimum</EM></A>

<DD> New-mail checking for a
<A HREF="config-notes.html#maildrop">Mail Drop</A>
is a little different from new
mail checking for a regular folder.
One of the differences is that the connection to the Mail Drop is not
kept open and so the cost of checking
(delay for you and additional load for the server) may be significant.
Because of this additional cost we set a minimum time that
must pass between checks.
This minimum only applies to the automatic checking done by <EM>Alpine</EM>.
If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are
at the end of a folder index, then the check is done right away.
<P>
This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop
new-mail checks.
You may want to set this minimum high in order to avoid experiencing some
of the delays associated with the checks.
Note that the time between checks is still controlled by the regular
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A> option.
When <EM>Alpine</EM> is about to do an automatic check for new mail (because
the Mail-Check-Interval has expired) then if the time since the last
new-mail check
of any open Mail Drops has been greater than the MailDrop-Check-Minimum,
the Mail Drop is checked for new mail as well.
Therefore, it is only useful to set this option to a value that is higher
than the Mail-Check-Interval.
<P>
If this option is set to zero, automatic Mail Drop new-mail
checking is disabled.
There is a minimum value, normally 60 seconds.
The default value is normally 60 seconds as well.
This applies to the INBOX and to the currently open folder if that is
different from the INBOX.
<P>

<DT> <A NAME="max-remote-connections"><EM>max-remote-connections</EM></A>

<DD> This option affects low-level behavior of <EM>Alpine</EM>.
The default value for this option is <EM>2</EM>.
If your INBOX is accessed using the IMAP protocol
from an IMAP server, that connection is kept open throughout the
duration of your <EM>Alpine</EM> session, independent of the value of this option.
The same is true of any 
<A HREF="#stay-open-folders">Stay-Open-Folders</A>
you have defined.
This option controls <EM>Alpine</EM>'s behavior when connecting to remote IMAP folders
other than your INBOX or your Stay-Open-Folders.
It specifies the maximum number of remote IMAP connections (other than
those mentioned above) that <EM>Alpine</EM> will use for accessing the rest of your
folders.
If you set this option to zero, you will turn off most remote connection
re-use.
It's difficult to understand exactly what this option does, and it is usually
fine to leave it set to its default value.
It is probably more likely that you will be interested in setting the
<A HREF="#stay-open-folders">Stay-Open-Folders</A> option
instead of changing the value of this option.
A slightly longer explanation of what is going on with this option
is given in the next paragraphs.

<P>
There are some time costs involved in opening and closing remote IMAP 
folders, the main costs being the time you have to wait for the connection
to the server and the time for the folder to open.
Opening a folder may involve not only the time the server takes to do its
processing but time that <EM>Alpine</EM> uses to do filtering.
These times can vary widely.
They depend on how loaded the server is, how large
the folder being opened is, and how you set up filtering, among other things.
Once <EM>Alpine</EM> has opened a connection to a particular folder, it will attempt
to keep that connection open in case you use it again.
In order to do this,
<EM>Alpine</EM> will attempt to use the Max-Remote-Connections (the value of
this option) IMAP connections you have allotted for this purpose.
<P>
For example, suppose the value of this option is set to &quot;2&quot;.
If your INBOX is accessed on a remote server using the IMAP protocol, that
doesn't count as one of the remote connections but it is always kept open.
If you then open another IMAP folder, that would be your first
remote connection counted as one of the Max-Remote-Connections connections.
If you open a third folder the second will be left open, in case you
return to it.
You won't be able to tell it has been left open.
It will appear to be closed when you leave the folder but the connection
will remain in the background.
Now suppose you go back to the second folder (the first folder after the
INBOX).
A connection to that folder is still open so you won't have to wait
for the startup time to open it.
Meanwhile, the connection to the third folder will be left behind.
Now, if you open a fourth folder, you will bump into the
Max-Remote-Connections limit, because this will be the third folder other
than INBOX and you have the option set to &quot;2&quot;.
The connection that is being used for
the third folder will be re-used for this new fourth folder.
If you go back to the third folder after this, it is no longer already
connected when you get there.
You'll still save some time since <EM>Alpine</EM> will re-use the connection to the
fourth folder and you have already logged in on that connection,
but the folder will have to be re-opened from scratch.
<P>
If a folder is large and the startup cost is dominated by the time it takes
to open that folder or to run filters on it, then it will pay to make the
value of this option large enough to keep it open.
On the other hand, if you only revisit a handful of folders or if
the folders are small, then it might
make more sense to keep this number small so that the reconnect
time (the time to start up a new connection and authenticate)
is eliminated instead.
<P>
You may also need to consider the impact on the server.
On the surface, a larger number here may cause a larger impact on the
server, since you will have more connections open to the server.
On the other hand, not only will <EM>you</EM> be avoiding the startup costs
associated with reopening a folder, but the <EM>server</EM> will be
avoiding those costs as well.
<P>
When twenty five minutes pass without any active use of an IMAP connection
being saved for possible re-use, that connection will be shut down,
<P>
This option is displayed as &quot;Maximum Remote Connections&quot;.
<P>

<DT> <A NAME="meta-message-background-color"><EM>meta-message-background-color</EM></A>
<DT> <A NAME="meta-message-foreground-color"><EM>meta-message-foreground-color</EM></A>

<DD> <A HREF="#meta-message-color"><EM>Meta-message Color</EM></A>.
<P>

<DT> <A NAME="mimetype-search-path"><EM>mimetype-search-path</EM></A>

<DD> This variable is used to replace <EM>Alpine</EM>'s default mime.types file
search path.  It takes one or more file names (full paths must be
specified) in which to look for file-name-extension to MIME type mapping
data.  See the Config Notes for details on <EM>Alpine</EM>'s usage of the <A
HREF="config-notes.html#mime.types">MIME.Types File</A>.  <P>

<DT> <A NAME="new-version-threshold"><EM>new-version-threshold</EM></A>

<DD> When a new version of <EM>Alpine</EM> is run for the first time it offers a
special explanatory screen to the user upon startup.  This option
helps control when and if that special screen appears for users that
have previously run <EM>Alpine</EM>.  It takes as its value a <EM>Alpine</EM> version
number.  <EM>Alpine</EM> versions less than the specified value will suppress this
special screen while versions equal to or greater than that specified
will behave normally. <P>

<DT> <A NAME="newmail-fifo-path"><EM>newmail-fifo-path</EM></A>

<DD> This option is only available in UNIX <EM>Alpine</EM>.
However, there is a very similar feature built in to <EM>PC-Alpine</EM>.
In <EM>PC-Alpine</EM>'s Config menu at the top of the screen
is an option called &quot;New Mail Window&quot;.
<P>
You may have <EM>Alpine</EM> create a FIFO special file (also called a named pipe, see mkfifo(3) and fifo(4)) where
it will send a one-line message each time a new message is received in
the current folder, the INBOX, or any open
<A HREF="#stay-open-folders">Stay-Open-Folders</A>.
To protect against two different <EM>Alpine</EM>s both writing to the same FIFO, <EM>Alpine</EM>
will only create the FIFO and write to it if it doesn't already exist.
<P>
A possible way to use this option would be to have a separate window
on your screen running the command
<P>
<CENTER><SAMP>cat filename</SAMP></CENTER>
<P>
where &quot;filename&quot; is the name of the file given for this option.
Because the file won't exist until after you start <EM>Alpine</EM>, you must <EM>first</EM>
start <EM>Alpine</EM> and <EM>then</EM> run the &quot;cat&quot; command.
You may be tempted to use &quot;tail -f filename&quot; to view the new
mail log.
However, the common implementations of the tail command will not do what you
are hoping.
<P>
The width of the messages produced for the FIFO may be altered with the
<A HREF="#newmail-window-width">NewMail-Window-Width</A> option.
<P>
On some systems, fifos may only be created in a local filesystem.
In other words, they may not be in NFS filesystems.
This requirement is not universal.
If the system you are using supports it, it should work.
(It is often the case that your home directory is in an NFS filesystem.
If that is the case, you might try using a file in the &quot;/tmp&quot;
filesystem, which is usually a local filesystem.)
Even when it is possible to use an NFS-mounted filesystem as a place to name
the fifo (for example, your home directory), it will still be the case that
the reader (probably the &quot;cat&quot; command) and the
writer (<EM>Alpine</EM>) of the fifo must be running on the same system. <P>

<DT> <A NAME="newmail-window-width"><EM>newmail-window-width</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
This option is only useful if you have turned on the
<A HREF="#newmail-fifo-path">NewMail-FIFO-Path</A> option.
That option causes new mail messages to be sent to a fifo file.
Those messages will be 80 characters wide by default.
You can change the width of the messages by changing this option.
For example, if you are reading those messages in another window you might
want to set this width to the width of that other window. <P>
For UNIX <EM>Alpine</EM>, this option is only useful if you have turned on the
<A HREF="#newmail-fifo-path">NewMail-FIFO-Path</A> option.
That option causes new mail messages to be sent to a fifo file.
Those messages will be 80 characters wide by default.
You can change the width of those messages by changing this option.
For example, if you are reading those messages in another window you might
want to set this width to the width of that other window.
<P>
If you are using <EM>PC-Alpine</EM>, it has an option in the Config menu to turn
on the &quot;New Mail Window&quot;.
The present option also controls the width of that window.

<DT> <A NAME="news-active"><EM>news-active-file-path</EM></A>

<DD> This option tells <EM>Alpine</EM> where to look for the "active file" for
newsgroups when accessing news locally, rather than via NNTP.  The default
path is usually <CODE>/usr/lib/news/active</CODE>. <P>

<DT> <A NAME="news-coll"><EM>news-collections</EM></A>

<DD> This is a list of collections where news folders are located.  See
the section describing <A HREF="config-notes.html#collections">collections</A>
for more information.  <P>

<DT> <A NAME="news-spool"><EM>news-spool-directory</EM></A>

<DD> This option tells <EM>Alpine</EM> where to look for the "news spool" for
newsgroups when accessing news locally, rather than via NNTP.  The default
path is usually <CODE>/usr/spool/news</CODE>. <P>

<DT> <A NAME="newsrc-path"><EM>newsrc-path</EM></A>

<DD> This option overrides the default name <EM>Alpine</EM> uses for your "newsrc" 
news status and subscription file.  If set, <EM>Alpine</EM> will take this value as
the full pathname for the desired newsrc file. <P>

<DT> <A NAME="nntp-range"><EM>nntp-range</EM></A>

<DD> This option applies only to newsgroups accessed using the NNTP protocol.
It does not, for example,
apply to newsgroups accessed using an IMAP-to-NNTP proxy.
<P>
When you open a connection to a News server using the NNTP protocol, you
normally have access to all of the articles in each newsgroup.
If a server keeps a large backlog of messages it may speed performance
some to restrict attention to only the newer messages in a group.
This option allows you to set how many article numbers should be checked
when opening a newsgroup.
You can think of &quot;nntp-range&quot; as specifying the maximum number
of messages you ever want to see.
For example, if you only ever wanted to look at the last 500 messages in each
newsgroup you could set this option to 500.
In actuality, it isn't quite that.
Instead, for performance reasons, it specifies the range of article
numbers to be checked, beginning
with the highest numbered article and going backwards from there.
If there are messages that have been canceled or deleted
their article numbers are still counted as part of the range.
<P>
So, more precisely, setting the &quot;nntp-range&quot; will cause article
numbers
<P><CENTER>last_article_number - nntp-range + 1 through last_article_number</CENTER>
<P>
to be considered when reading a newsgroup.
The number of messages that show up in your index will be less than or equal
to the value of &quot;nntp-range&quot;.
<P>
The purpose of this option is simply to speed up access when reading news.
The speedup comes because <EM>Alpine</EM> can ignore all but the last nntp-range article
numbers, and can avoid downloading any information about the ignored articles.
There is a cost you pay for this speedup.
That cost is that there is no way for you to see those ignored articles.
The articles that come before the range you specify are invisible to you and
to <EM>Alpine</EM>, as if they did not exist at all.
There is no way to see those messages using, for example, an unexclude command
or something similar.
The only way to see those articles is to set this option high enough (or
set it to zero) and then to reopen the newsgroup.

<P>
If this option is set to 0 (which is also the default),
then the range is unlimited.
This option applies globally to all NNTP servers and to all newsgroups
on those servers.
There is no way to set different values for different newsgroups or servers.
<P>

<DT> <A NAME="nntp-server"><EM>nntp-server</EM></A>

<DD> One or more NNTP servers (host name or IP address) which <EM>Alpine</EM> will
use for reading and posting news.
If you read and post news to and from a single
NNTP server, you can get away with only setting the <EM>nntp-server</EM>
variable and leaving the <EM>news-collections</EM> variable unset.
<P>
When you define an NNTP server, <EM>Alpine</EM> implicitly defines a
news collection for you, assuming that server as the news server
and assuming that you will use the NNTP protocol and a local newsrc
configuration file for reading news.
See also <A HREF="#configuring-news">Configuring News</A>.
<P>
Your NNTP server may offer NNTP &quot;AUTHINFO SASL&quot;
or &quot;AUTHINFO USER&quot; authentication.
It may even require it.
If your NNTP server does offer such authentication you may specify a user name
parameter to cause <EM>Alpine</EM> to attempt to authenticate.
The same is true for the server name in a folder collection which uses NNTP.
This parameter requires an associated value,
the username identifier with which to establish the server connection.
An example might be:

<P>
<CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER>
<P>

If authentication is offered by the server, this will cause <EM>Alpine</EM> to
attempt to use it.
If authentication is not offered by the server, this will cause <EM>Alpine</EM>
to fail with an error similar to:

<P>
<CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER>
<P>
For more details about the server name possibilities see
<A HREF="config-notes.html#server-name-syntax">Server Name Syntax</A>.
<P>

<DT> <A NAME="norm-back"><EM>normal-background-color</EM></A>
<DT> <A NAME="normal-foreground-color"><EM>normal-foreground-color</EM></A>

<DD> <A HREF="#normal-color"><EM>Normal Color</EM></A>.
<P>

<DT> <A NAME="opening-text-separator-chars"><EM>opening-text-separator-chars</EM></A>
<DD> This option controls a minor aspect of <EM>Alpine</EM>'s MESSAGE INDEX screen.
With some setups the text of the subject is followed
by the opening text of the message if there is any room available in the index line.
If you have configured your
<A HREF="#index-format"><EM>Index-Format</EM></A> option
to include one of the Subject tokens which causes this behavior
(SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used
to modify what is displayed slightly.
By default, the Subject is separated from the opening text of the message by
the three characters space dash space;
<P>
<CENTER><SAMP>&quot;&nbsp;-&nbsp;&quot;</SAMP></CENTER>
<P>
Use this option to set it to something different.
The value must be quoted if it includes any space characters.
For example, the default value could be specified explicitly by setting this
option to
<P>
<CENTER><SAMP>Opening-Text-Separator-Chars="&nbsp;-&nbsp;"</SAMP></CENTER>
<P>
This option is displayed as &quot;Opening Text Separator Characters&quot;.
<P>

<DT> <A NAME="operating-dir"><EM>operating-dir</EM></A>

<DD> System-wide <EM>Alpine</EM> configuration files only.
This names the root of the
tree to which the user is restricted when reading and writing folders and
files. It is usually used in the <EM>fixed</EM> configuration file. <P>

<DT> <A NAME="patterns-filters2"><EM>patterns-filters2</EM></A>

<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used with
<A HREF="#filter-config"><EM>Filtering</EM></A>.
This variable is normally maintained through the Setup/Rules/Filters
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a filters file is to use the InsertFile command in
the Setup/Rules/Filters screen with a filename which doesn't yet exist.
Then use the Shuffle command to move existing filter patterns into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
The purpose of filter files is for sharing filters.
<P>
This option is displayed as &quot;Patterns Filters&quot;.
<P>

<DT> <A NAME="patterns-indexcolors"><EM>patterns-indexcolors</EM></A>

<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used for
<A HREF="#index-color-config"><EM>Index Line Colors</EM></A>.
This variable is normally maintained through the Setup/Rules/Indexcolor
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a indexcolor file is to use the InsertFile command in
the Setup/Rules/Indexcolor screen with a filename which doesn't yet exist.
Then use the Shuffle command to move existing patterns into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
The purpose of indexcolor files is for sharing indexcolors.
<P>

<DT> <A NAME="patterns-other"><EM>patterns-other</EM></A>

<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used with
<A HREF="#other-config"><EM>Miscellaneous Rules</EM></A> configuration.
This variable is normally maintained through the Setup/Rules/Other
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a rules file is to use the InsertFile command in
the Setup/Rules/Other screen with a filename which doesn't yet exist. Then use
the Shuffle command to move existing rules into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
<P>

<DT> <A NAME="patterns-roles"><EM>patterns-roles</EM></A>

<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used with
<A HREF="#role-config"><EM>Roles</EM></A>.
This variable is normally maintained through the Setup/Rules/Roles
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a roles file is to use the InsertFile command in
the Setup/Rules/Roles screen with a filename which doesn't yet exist. Then use
the Shuffle command to move existing roles into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
The purpose of role files is for sharing roles.
<P>

<DT> <A NAME="patterns-scores2"><EM>patterns-scores2</EM></A>

<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used with
<A HREF="#scoring-config"><EM>Scoring</EM></A>.
This variable is normally maintained through the Setup/Rules/SetScores
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a scores file is to use the InsertFile command in
the Setup/Rules/SetScores screen with a filename which doesn't yet exist.
Then use the Shuffle command to move existing scoring patterns into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
The purpose of scoring files is for sharing scoring rules.
<P>
This option is displayed as &quot;Patterns Scores&quot;.
<P>

<DT> <A NAME="patterns-search"><EM>patterns-search</EM></A>

<DD> Matching patterns for use with the Select command are stored in
this variable.
These patterns are used with
<A HREF="#search-rules-config"><EM>Search Rules</EM></A> configuration.
This variable is normally maintained through the Setup/Rules/searCh
configuration screen.
It is a list variable.
Each member of the list is a single pattern, or it can be
a file which contains zero or more lines of patterns.
The only way to create a rules file is to use the InsertFile command in
the Setup/Rules/searCh screen with a filename which doesn't yet exist. Then use
the Shuffle command to move existing rules into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
<P>

<DT> <A NAME="personal-name"><EM>personal-name</EM></A>

<DD> Personal configuration file only.
User's full personal name.  On UNIX systems, the default is taken
from the accounts data base (<CODE>/etc/passwd</CODE>).
The easiest way to change the full From address is with the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable.
<P>

<DT> <A NAME="personal-print-category"><EM>personal-print-category</EM></A>

<DD> Personal configuration file only.
This is the category that the default print command belongs to. There
are three categories. Category 1 is an attached printer which uses the ANSI
escape sequence, category 2 is the standard system print command, and
category 3 is the set of custom printer commands defined by the user.
This just helps <EM>Alpine</EM> figure out where to put the cursor when the user
runs the <EM>Setup/Printer</EM> command. This is not used by <EM>PC-Alpine</EM>.
<P>

<DT> <A NAME="personal-print-command"><EM>personal-print-command</EM></A>

<DD> Personal configuration file only.
This corresponds to the third category in the printer menu, the
personally selected print commands. This variable
contains the list of custom commands that the user has entered in the
<EM>Setup/Printer</EM> screen. This is not used by <EM>PC-Alpine</EM>.
<P>

<DT> <A NAME="posting-char-set"><EM>posting-character-set</EM></A>

<DD> See the discussion in
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for
details.<P>

<DT> <A NAME="postponed-folder"><EM>postponed-folder</EM></A>

<DD> The folder where postponed messages are stored.  The default is
<EM>postponed-msgs</EM> (Unix) or <EM>POSTPOND</EM> (PC).  <P>

<DT> <A NAME="print-font-name"><EM>print-font-name</EM></A>

<DD> Winsock version of <EM>PC-Alpine</EM> only.  <P>

<DT> <A NAME="print-font-size"><EM>print-font-size</EM></A>

<DD> Winsock version of <EM>PC-Alpine</EM> only.  <P>

<DT> <A NAME="print-font-style"><EM>print-font-style</EM></A>

<DD> Winsock version of <EM>PC-Alpine</EM> only.  <P>

<DT> <A NAME="printer"><EM>printer</EM></A>

<DD> Personal configuration file only.
This is the current setting for a user's printer. 
This variable is set from <EM>Alpine</EM>'s <EM>Setup/Printer</EM> screen.
<P>

<DT> <A NAME="prompt-background-color"><EM>prompt-background-color</EM></A>
<DT> <A NAME="prompt-foreground-color"><EM>prompt-foreground-color</EM></A>

<DD> <A HREF="#prompt-color"><EM>Prompt Color</EM></A>.
<P>

<DT> <A NAME="pruned-folders"><EM>pruned-folders</EM></A>

<DD> This variable allows you to define a list of one or more folders that
<EM>Alpine</EM> will offer to prune for you in the same way it automatically offers
to prune your "sent-mail" folder each month.
Each folder in this list must be a folder in your default folder collection
(the first folder collection if you have more than one), and it is just
the relative name of the folder in the collection, not the fully-qualified name.
It is similar to sent-mail.
Instead of something like
<P>
<CENTER><SAMP>pruned-folders={servername}mail/folder</SAMP></CENTER>
<P>
the correct value to use would be
<P>
<CENTER><SAMP>folder</SAMP></CENTER>
<P>
There is an assumption here that your first collection is the folders in
<P>
<CENTER><SAMP>{servername}mail</SAMP></CENTER>
<P>

Once a month, for each folder listed, <EM>Alpine</EM> will offer to move
the contents of the folder to a new folder of the same name but with
the previous month's date appended.  <EM>Alpine</EM> will then look for any such
date-appended folder names created for a previous month, and offer each
one it finds for deletion.
<P>

If you decline the first offer, no mail is moved and no new folder is
created.
<P>

The new folders will be created
in your default folder collection.
<P>

<DT> <A NAME="pruning-rule"><EM>pruning-rule</EM></A>

<DD> By default, <EM>Alpine</EM> will ask at the beginning of each month whether or not
you want to rename your sent-mail folder to a name like sent-mail-month-year.
(See the feature <A HREF="#prune-uses-yyyy-mm">prune-uses-yyyy-mm</A> to
change the format of the folder to sent-mail-yyyy-mm.)
It will also ask whether you would like to delete old sent-mail folders.
If you have defined
<A HREF="#read-msg-fold"><EM>read-message-folder</EM></A>
or
<A HREF="#pruned-folders"><EM>pruned-folders</EM></A>
<EM>Alpine</EM> will also ask about pruning those folders.
With this option you may provide an automatic answer to the rename questions
and you may tell <EM>Alpine</EM> to not ask about deleting old folders.<P>

<DT> <A NAME="quote1-background-color"><EM>quote1-background-color</EM></A>
<DT> <A NAME="quote1-foreground-color"><EM>quote1-foreground-color</EM></A>
<DT> <A NAME="quote2-background-color"><EM>quote2-background-color</EM></A>
<DT> <A NAME="quote2-foreground-color"><EM>quote2-foreground-color</EM></A>
<DT> <A NAME="quote3-background-color"><EM>quote3-background-color</EM></A>
<DT> <A NAME="quote3-foreground-color"><EM>quote3-foreground-color</EM></A>

<DD> <A HREF="#quote-colors"><EM>Quote Colors</EM></A>.
<P>

<DT> <A NAME="quote-replace-string"><EM>quote-replace-string</EM></A>

<DD> This option specifies what string to use as a quote when <b>viewing</b> a
message.  The standard way of quoting messages when replying is the string
&quot;&gt;&nbsp;&quot; (quote space).
With this variable set, viewing a message will
replace occurrences of &quot;&gt;&nbsp;&quot; with the replacement string.
This setting works best when
<A HREF="#reply-ind-string">Reply-Indent-String</A>
or the equivalent setting in your correspondents' mail programs
is set to the default &quot;&gt;&nbsp;&quot;, but it will also work fine with the
Reply-Indent-String set to &quot;&gt;&quot;.
<P>
Enable the feature
<A HREF="#quote-replace-nonflowed">Quote-Replace-Nonflowed</A>
to also have quote-replacement performed on non-flowed messages.
<P>
Setting this option will replace  &quot;&gt;&quot; and 
&quot;&gt;&nbsp;&quot; with the new setting. This string may include trailing
spaces. To preserve those spaces enclose the full string in double quotes.
<P>
No padding to separate the text of the message from the quote string is
added. This means that if you do not add trailing spaces to the value of
this variable, text will be displayed right next to the quote string,
which may be undesirable. This can be avoided by adding a new string
separated by a space from your selection of quote string replacement. This
last string will be used for padding. For example, setting this variable to 
&quot;&gt;&quot;&nbsp;&quot; &quot; has the effect of setting
&quot;&gt;&quot; as the quote-replace-string, with the text padded by
a space from the last quote string to make it more readable.
<P>
One possible setting for this variable could be
&quot;&nbsp;&nbsp;&nbsp;&nbsp;&quot; (four spaces wrapped in quotes), which
would have the effect of indenting each level of quoting four spaces and
removing the &quot;&gt;&quot;'s.  Different levels of quoting could be made
more discernible by setting colors for quoted text.
<P>
Replying to or forwarding the viewed message will preserve the original
formatting of the message, so quote-replacement will not be performed on
messages that are being composed.
<P>

<DT> <A NAME="quote-suppression-threshold"><EM>quote-suppression-threshold</EM></A>

<DD> This option should be used with care.
It will cause some of the quoted text to be eliminated from the
display when viewing a message in the MESSAGE TEXT screen.
For example, if you set the Quote-Suppression-Threshold to the
value &quot;5&quot;,
this will cause quoted text that is longer than five lines to be truncated.
Quoted text of five or fewer consecutive lines will be displayed in its entirety.
Quoted text of more than six lines will have the first five lines displayed
followed by a line that looks something like
<P>
<CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
<P>
As a special case, if exactly one line of quoted text would be hidden, the
entire quote will be shown instead.
So for the above example, quoted text which is exactly six lines long will
will be shown in its entirety.
(In other words, instead of hiding a single line and adding a line
that announces that one line was hidden, the line is just shown.)
<P>
If the sender of a message has carefully chosen the quotes that he or she
includes, hiding those quotes may change the meaning of the message.
For that reason, <EM>Alpine</EM> requires that when you want to set the value of this
variable to something less than four lines, you actually have to set it
to the negative of that number.
So if you want to set this option to &quot;3&quot;, you actually have to
set it to &quot;-3&quot;.
The only purpose of this is to get you to think about whether or not you
really want to do this!
If you want to delete all quoted text you set the value of this option
to the special value &quot;-10&quot;.
<P>
The legal values for this option are
<P>
<TABLE>   
<TR>
  <TD> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </TD>
  <TD> Default, don't hide anything </TD>
</TR>
<TR>
  <TD> &nbsp;-1,-2,-3&nbsp;&nbsp; </TD>
  <TD> Suppress quote lines past 1, 2, or 3 lines </TD>
</TR>
<TR>
  <TD> &nbsp;4,5,6,...&nbsp; </TD>
  <TD> Suppress if more than that many lines </TD>
</TR>
<TR>
  <TD> &nbsp;&nbsp;&nbsp;-10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </TD>
  <TD> Suppress all quoted lines </TD>
</TR>
</TABLE>
<P>
If you set this option to a non-default value you may sometimes wish to
view the quoted text that is not shown.
When this is the case, the HdrMode (Header Mode) command may be used to
show the hidden text.
Typing the &quot;H&quot; command once will show the hidden text.
Typing a second &quot;H&quot; will also turn on Full Header mode.
The presence or absence of the HdrMode command is determined by the
<A HREF="#enable-full-header-cmd">&quot;Enable-Full-Header-Cmd&quot;</A>
Feature-List option in your <EM>Alpine</EM> configuration, so you will want to
be sure that is turned on if you use quote suppression.
<P>
For the purposes of this option, a quote is a line that begins with the
character &quot;&gt;&quot;.
<P>
Quotes are only suppressed when displaying a message on the screen.
The entire quote will be left intact when printing or forwarding or something
similar.
<P>

<DT> <A NAME="read-msg-fold"><EM>read-message-folder</EM></A>

<DD> If set, mail in the <EM>INBOX</EM> that has been read but not deleted
is moved here, or rather, the user is asked whether or not he or she wants
to move it here upon quitting <EM>Alpine</EM>.  <P>

<DT> <A NAME="remote-abook-history"><EM>remote-abook-history</EM></A>

<DD> Sets how many extra copies of
<A HREF="low-level.html#addrbook">remote address book</A>
data will be kept in each remote address book folder.
The default is three.
These extra copies are simply old versions of the data. Each time a change
is made a new copy of the address book data is appended to the folder. Old
copies are trimmed, if possible, when <EM>Alpine</EM> exits.
An old copy can be put back into use by
deleting and expunging newer versions of the data from the folder.
Don't delete the first message from the folder. It is a special header
message for the remote address book and it must be there.
This is to prevent regular folders from being used as remote address book
folders and having their data destroyed.
<P>

<DT> <A NAME="remote-abook-metafile"><EM>remote-abook-metafile</EM></A>

<DD> Personal configuration file only.
This is usually set by <EM>Alpine</EM> and is the name of a file
that contains data about
<A HREF="low-level.html#addrbook">remote address books</A> and
<A HREF="low-level.html#remote-config">remote configuration files</A>.
<P>

<DT> <A NAME="remote-abook-validity"><EM>remote-abook-validity</EM></A>

<DD> Sets the minimum number of minutes that a
remote address book will be considered up to date.
Whenever an entry contained in a remote address book is used,
if more than this many minutes have
passed since the last check the remote server will be queried to see if the
address book has changed.
If it has changed, the local copy is updated.
The default value is five minutes.
The special value of -1 means never check.
The special value of zero means only check when the address book is first
opened.
<P>
No matter what the value, the validity check is always done when the
address book is about to be changed by the user.
The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L)
while in the address book maintenance screen for the remote address book.
<P>

<DT> <A NAME="reply-ind-str"><EM>reply-indent-string</EM></A>

<DD> This variable specifies an aspect of <EM>Alpine</EM>'s <EM>Reply</EM>
command.
When a message is replied to and the text of the message is included, the
included text usually has the string &quot;&gt; &quot; prepended
to each line indicating it is quoted text.
 
<P>
This option specifies a different value for that string.
If you wish to use a string which begins or ends with a space,
enclose the string in double quotes.
 
<P>
Besides simple text, the prepended string can be based
on the message being replied to.
The following tokens are substituted for the message's corresponding value:

<DL>
<DT>_FROM_</DT>
<DD>This token gets replaced with the message sender's &quot;username&quot;.
At most six characters are used.
</DD>

<DT>_NICK_</DT>
<DD>This token gets replaced with the nickname of the message sender's
address as found in your addressbook.
If no addressbook entry is found,
Pine replaces the characters &quot;_NICK_&quot; with nothing.
At most six characters are used.
</DD>

<DT>_INIT_</DT>
<DD>This token gets replaced with the initials of the sender of the message.
</DD>

</DL>

When the
<A HREF="#enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A>
feature is enabled, you are given the opportunity to edit the string, whether 
it is the default or one automatically generated using the above tokens.
<P>

<DT> <A NAME="reply-leadin"><EM>reply-leadin</EM></A>

<DD> This option is used to customize the content of the introduction line
that is included when replying to a message and including the original
message in the reply.
The normal default (what you will get if you delete this variable) looks
something like:
<P>
<CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
<P>
where the day of the week is only included if it is available in the
original message.
You can replace this default with text of your own.
The text may contain tokens that are replaced with text
that depends on the message you are replying to.
For example, the default is equivalent to:
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
<P>

Since this variable includes regular text mixed with special tokens
the tokens have to be surrounded by underscore characters.
For example, to use the token &quot;<SAMP>PREFDATE</SAMP>&quot;
you would need to use &quot;<SAMP>_PREFDATE_</SAMP>&quot;,
not &quot;<SAMP>PREFDATE</SAMP>&quot;.
<P>
The list of available tokens is
<A HREF="#index-tokens"><EM>here</EM></A>.

<P>
By default, the text is all on a single line and is followed by a blank line.
If your <EM>Reply-Leadin</EM> turns out to be longer
than 80 characters when replying to a particular message, it is shortened.
However, if you use the token
<P>
<CENTER><SAMP>_NEWLINE_</SAMP></CENTER>
<P>

anywhere in the value, no end of line or blank line is appended, and no
shortening is done.
The _NEWLINE_ token may be used to get rid of the blank line following
the text, to add more blank lines, or to form a multi-line
<EM>Reply-Leadin</EM>.
To clarify how _NEWLINE_ works recall that the default value is:
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
<P>

That is equivalent to
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER>
<P>

In the former case, two newlines are added automatically because
no _NEWLINE_ token appears in the value of the option (for backwards
compatibility). In the latter case, the newlines are explicit.
If you want to remove the blank line that follows the
<EM>Reply-Leadin</EM> text use a single
_NEWLINE_ token like
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER>
<P>

Because of the backwards compatibility problem, it is not possible to
remove all of the ends of lines, because then there will be no _NEWLINE_ tokens
and that will cause the automatic adding of two newlines!
If you want, you may embed newlines in the middle of the text, as well,
producing a multi-line <EM>Reply-Leadin</EM>.

<P>
By default, no attempt is made to localize the date.
If you prefer a localized form you may find that one of the tokens
_PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute.
If you want more control one of the many other date tokens, such as _DATEISO_,
might be better.

<P>
For the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="#reply-token-conditionals"><EM>here</EM></A>.

<P>
In the very unlikely event that you want to include a literal token
in the introduction line you must precede it with a backslash character.
For example,
<P>
<CENTER><SAMP>&#92;_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
<P>
would produce something like
<P>
<CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
<P>
It is not possible to have a literal backslash followed by an expanded token.
<P>
 
<DT> <A NAME="reverse-background-color"><EM>reverse-background-color</EM></A>
<DT> <A NAME="reverse-foreground-color"><EM>reverse-foreground-color</EM></A>

<DD> <A HREF="#reverse-color"><EM>Reverse Color</EM></A>.
<P>

<DT> <A NAME="rsh-command"><EM>rsh-command</EM></A>

<DD> Sets the format of the command used to
open a UNIX remote shell connection. The default is
"%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
provided command. The first is for the command's pathname, the second is
for the host to connect to, the third is for the user to connect as, and
the fourth is for the connection method (typically <CODE>imap</CODE>).
<P>

<DT> <A NAME="rsh-open-timeout"><EM>rsh-open-timeout</EM></A>

<DD> Sets the time in seconds that <EM>Alpine</EM> will
attempt to open a UNIX remote shell connection.
The default is 15, the minimum non-zero value is 5,
and the maximum is unlimited. If this is set to zero rsh connections
will be completely disabled.
<P>

<DT> <A NAME="rsh-path"><EM>rsh-path</EM></A>

<DD> Sets the name of the command used to open a UNIX remote shell
connection. The default is typically <CODE>/usr/ucb/rsh</CODE>.
<P>

<DT> <A NAME="saved-msg-name"><EM>saved-msg-name-rule</EM></A>

<DD> Determines default folder name when <EM>Sav</EM>ing.
If set to <EM>default-folder</EM> (which is the default setting),
then <EM>Alpine</EM> will offer the folder "saved-messages" (UNIX) or "SAVEMAIL" 
(PC) for <EM>Sav</EM>ing messages. The default folder offered in this way
may be changed by using the configuration variable
<A HREF="#def-save"><EM>default-saved-msg-folder</EM></A>.
<P>

If this rule is set to <EM>last-folder-used</EM>, <EM>Alpine</EM> offers to
<EM>Save</EM> to the folder you last successfully <EM>Saved</EM> a message
to (this session).
The first time you <EM>Save</EM> a message in a session,
<EM>Alpine</EM> offers to <EM>Save</EM> the message to the default folder.
<P>

Choosing any of the <EM>by-</EM> options causes <EM>Alpine</EM> to attempt
to get the chosen option's value for the message being <EM>Saved</EM> (or
for the first message being Saved if using an aggregate Save).
For example, if <EM>by-from</EM> is chosen, <EM>Alpine</EM> attempts to
get the value of who the message
came from (i.e. the from address). <EM>Alpine</EM> then attempts to
<EM>Save</EM> the message to a folder matching that value.
If <EM>by-from</EM> is chosen and no value is
obtained, <EM>Alpine</EM> uses <EM>by-sender</EM>.
The opposite is also true.
If <EM>by-recipient</EM> was chosen and the message was posted to a newsgroup,
<EM>Alpine</EM> will use the newsgroup name. 
If <EM>by-replyto</EM> is chosen and no value is
obtained, <EM>Alpine</EM> uses <EM>by-from</EM>.
<P>
 
If any of the &quot;by-realname&quot; options are chosen, <EM>Alpine</EM> will attempt
to use the personal name part of the address instead of the mailbox part.
If any of the &quot;by-nick&quot; options are chosen, the
address is looked up in your address book and if found, the
nickname for that entry is used.
Only simple address book entries are checked, not distribution lists.
Similarly, if any of the
&quot;by-fcc&quot; options are chosen, the fcc from the corresponding
address book entry is used.
If by-realname, or the by-nick or by-fcc lookups result in no value,
then if the chosen option ends with the &quot;then-from&quot;,
&quot;then-sender&quot;, &quot;then-replyto&quot;,
or &quot;then-recip&quot; suffix, <EM>Alpine</EM>
reverts to the same behavior as &quot;by-from&quot;,
&quot;by-sender&quot;, &quot;by-replyto&quot;, or &quot;by-recip&quot;
depending on which option was specified.
If the chosen option doesn't end with one of
the &quot;then-&quot; suffixes, then <EM>Alpine</EM> reverts to the default
folder when no match is found in the address book.

<P>
Here is an example to make some of the options clearer.
If the message is From
<P>
<CENTER><SAMP>Fred Flintstone &lt;flint@bedrock.org&gt;</SAMP></CENTER>
<P>
and this rule is set to &quot;by-from&quot;, then the default folder offered
in the save dialog would be &quot;flint&quot;.
<P>
If this rule is set to &quot;by-realname-of-from&quot; then the default would
be &quot;Fred Flintstone&quot;.
<P>
If this rule is set to &quot;by-nick-of-from&quot; then <EM>Alpine</EM> will search
for the address &quot;flint@bedrock.org&quot; in your address book.
If an entry is found and it has a nickname associated with it, that nickname
will be offered as the default folder.
If not, the default saved message folder will be offered as the default.
<P>
If this rule is set to &quot;by-fcc-of-from&quot; then <EM>Alpine</EM> will search
for the address &quot;flint@bedrock.org&quot; in your address book.
If an entry is found and it has an Fcc associated with it, that Fcc
will be offered as the default folder.
If not, the default saved message folder will be offered as the default.
<P>
If this rule is set to &quot;by-nick-of-from-then-from&quot; then <EM>Alpine</EM> will search
for the address &quot;flint@bedrock.org&quot; in your address book.
If an entry is found and it has a nickname associated with it, that nickname
will be offered as the default folder.
If it is not found (or has no nickname) then the default offered will be
the same as it would be for the &quot;by-from&quot; rule.
That is, it would be &quot;flint&quot;
<P>
This option is displayed as &quot;Saved Message Name Rule&quot;.
<P>

<DT> <A NAME="scroll-margin"><EM>scroll-margin</EM></A>

<DD> This option controls when <EM>Alpine</EM>'s line-by-line scrolling occurs.
Typically, when a selected item is at the top or bottom screen edge
and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are pressed, the
displayed items are scrolled down or up by a single line.
<P>
 
This option allows you to tell <EM>Alpine</EM> the number of lines from the top and
bottom screen edge that line-by-line scrolling should occur. For example,
setting this value to one (1) will cause <EM>Alpine</EM> to scroll the display
when you move to select an item on the display's top or
bottom edge (instead of moving when you move off the edge of the screen).
<P>
  
By default, this variable is zero (0), indicating that scrolling happens
when you move up or down to select an item immediately off the display's
top or bottom edge.
<P>

<DT> <A NAME="selectable-item-background-color"><EM>selectable-item-background-color</EM></A>
<DT> <A NAME="selectable-item-foreground-color"><EM>selectable-item-foreground-color</EM></A>

<DD> <A HREF="#selectable-item-color"><EM>Selectable-item Color</EM></A>.
<P>

<DT> <A NAME="sending-filters"><EM>sending-filters</EM></A>

<DD> This option defines a list of text-filtering commands (programs and
scripts) that may be selectively invoked to process a message just before
it is sent.  If set, the Composer's <EM>^X Send</EM> command will allow you to
select which filter (or none) to apply to the message before it is sent. 
For security reasons, the full path of the filter program must be
specified.
<P>
Sending filters do not work with <EM>PC-Alpine</EM> and sending filters are
not used if the feature
<A HREF="#send-without-confirm">send-without-confirm</A> is set.
<P>
Command Modifying Tokens:

<DL>
<DT><EM>_RECIPIENTS_</EM>
<DD>When the command is executed, this token is replaced 
with the space delimited list of recipients of the 
message being sent. 
        
<DT><EM>_TMPFILE_</EM>
<DD>
When the command is executed, this token is 
replaced with the path and name of the temporary 
file containing the text to be filtered.  <EM>Alpine</EM> 
expects the filter to replace this data with the 
filter's result.

NOTE: Use of this token implies that the text to 
be filtered is not piped into standard input of the 
executed command and its standard output is ignored. 
<EM>Alpine</EM> restores the tty modes before invoking the
filter in case the filter interacts with the user
via its own standard input and output.  
                        
<DT><EM>_RESULTFILE_</EM>
<DD>When the command is executed, this token is 
replaced with the path and name of a temporary 
file intended to contain a status message from the 
filter. <EM>Alpine</EM> displays this in the message status 
field. 
 
<DT><EM>_DATAFILE_</EM>
<DD>When the command is executed, this token is replaced 
in the command line with the path and name of a 
temporary file that <EM>Alpine</EM> creates once per session 
and deletes upon exit.  The file is intended to be 
used by the filter to store state information between 
instances of the filter.
   
<DT><EM>_PREPENDKEY_</EM>
<DD>When the command is executed, this token indicates 
that a random number will be passed down the input 
stream before the message text. It is not included as a command-line argument.
This number could be used as a session key.  It is sent in this way 
to improve security.  The number is unique to the 
current <EM>Alpine</EM> session and is only generated once per 
session. 

<DT><EM>_INCLUDEALLHDRS_</EM>
<DD>When the command is executed, this token indicates 
that the headers of the message will be passed down the input stream
before the message text.
It is not included as a command-line argument.
The filter should, of course, remove the headers before returning control
to <EM>Alpine</EM>.

<DT><EM>_MIMETYPE_</EM>
<DD>When the command is executed, this token is replaced in the
command name with a temporary file name used to accept any new MIME
Content-Type information necessitated by the output of the filter.
Upon the filter's exit, if the file contains new MIME type
information, <EM>Alpine</EM> verifies its format and replaces the outgoing
message's MIME type information with that contained in the file. This
is basically a cheap way of sending something other than Text/Plain.
</DL>
<P>

<DT> <A NAME="sendmail-path"><EM>sendmail-path</EM></A>

<DD> This names the path to an
alternative program, and any necessary arguments, to be used in posting
mail messages.  See the section on <A
HREF="background.html#SMTP">SMTP and Sendmail</A> for more details.
<P>

<DT> <A NAME="sig-file"><EM>signature-file</EM></A></A>

<DD> This is the name of a file which will be automatically inserted into
outgoing messages.
It typically contains information such as your
name, email address and organizational affiliation.
<EM>Alpine</EM> adds the
signature into the message as soon as you enter the composer so you
can choose to remove it or edit it on a message by message basis.
Signature file placement in message replies is controlled by the
<A HREF="#sig-at-bot">signature-at-bottom</A>
setting in the feature list.
<P>

This defaults to
<CODE>~/.signature</CODE> on UNIX and &lt;PINERC
directory&gt;<CODE>\PINE.SIG</CODE> on a PC.  <P>

To create or edit your signature file choose Setup from the Main Menu
and then select S for Signature (Main/Setup/Signature).
This puts you
into the Signature Editor where you can enter a <EM>few</EM> lines of
text containing your identity and affiliation.

<P>
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>,
but the rest of the processing works as if the contents came from a file.

<P>
Instead of storing the data in a local file, the
signature data may be stored remotely in an IMAP folder.
In order to do this, 
you must use a remote name for the file.
A remote signature-file name might look like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER>
<P>
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/signature</SAMP></CENTER>
<P>

The syntax used here is the same as the syntax used for remote configuration
files from the command line.
Note that you may not access an existing signature file remotely,
you have to create a new <EM>folder</EM> which contains the signature data.
If the name you use here for the signature file is a remote name, then when
you edit the file from the Setup/Signature command the data will be stored
remotely in the folder.
You aren't required to do anything special to create the folder, it
gets created automatically if you use a remote name.

<P>
Besides regular text, the signature file may also contain
(or a signature program may produce) tokens which
are replaced with text which usually depends on the message you are replying
to or forwarding.
For example, if the signature file contains the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
anywhere in the text, then that token is replaced by the date
the message you are replying to or forwarding was sent.
If it contains
<P>
<CENTER><SAMP>_CURDATE_</SAMP></CENTER>
<P>
that is replaced with the current date.
The first is an example of a token which depends on the message you
are replying to (or forwarding) and the second is an example which
doesn't depend on anything other than the current date.
You have to be a little careful with this facility since tokens which
depend on the message you are replying to or forwarding will be replaced
by nothing in the case where you are composing a new message from scratch.
The use of <A HREF="#role-config"><EM>roles</EM></A> may help you
in this respect.
It allows you to use different signature files in different cases.
<P>

The list of tokens available for use in the signature file is
<A HREF="#index-tokens"><EM>here</EM></A>.
<P>

Instead of, or along with the use of <EM>roles</EM> to give you
different signature files in different situations, there is also
a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
This is explained in detail
<A HREF="#reply-token-conditionals"><EM>here</EM></A>.
This isn't for the faint of heart.
<P>
In the very unlikely event that you want to include a literal token
in the signature you must precede it with a backslash character.
For example,
<P>
<CENTER><SAMP>&#92;_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
<P>
would produce something like
<P>
<CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
<P>
It is not possible to have a literal backslash followed by an expanded token.
<P>

<DT> <A NAME="signature-background-color"><EM>signature-background-color</EM></A>
<DT> <A NAME="signature-foreground-color"><EM>signature-foreground-color</EM></A>

<DD> <A HREF="#signature-color"><EM>Signature Color</EM></A>.
<P>

<DT> <A NAME="smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
If the option
<A HREF="#smime-public-cert-container"><EM>smime-public-cert-container</EM></A>
is set then this option will have no effect.
<P>
Normally, Public Certificates for use with S/MIME will be stored in the directory
which is the value of this option.
Those certificates will be stored in PEM format, one certificate per file.
The name of the file for the certificate corresponding to
<P>
<CENTER><SAMP>emailaddress</SAMP></CENTER>
<P>
should be
<P>
<CENTER><SAMP>emailaddress.crt</SAMP></CENTER>
<P>
For example, a file for user@example.com would be in the file
<P>
<CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
<P>
in this directory.
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
Typically, the public certificates that you have will come from S/MIME signed
messages that are sent to you.
<EM>Alpine</EM> will extract the public certificate from the signed message and store
it in the certificates directory.
These PEM format public certificates look something like:
<PRE>
-----BEGIN CERTIFICATE-----
MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB
rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug
Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho
...
2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8
D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf
-----END CERTIFICATE-----
</PRE>
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as &quot;S/MIME - Public Cert Directory&quot;.
<P>

<DT> <A NAME="smime-public-cert-container"><EM>smime-public-cert-container</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
If this option is set it will be used instead of
<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>
<P>
This option gives you a way to store certificates remotely on an IMAP server
instead of storing the certificates one per file locally.
In order to do that you just give this option a remote folder name for a folder
which does not yet exist.
The name is similar to the name you might use for a remote configuration file.
A remote folder name might look something like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER>
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as &quot;S/MIME - Public Cert Container&quot;.
<P>

<DT> <A NAME="smime-private-key-directory"><EM>smime-private-key-directory</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
In order to sign outgoing S/MIME messages you will need a
personal digital ID certificate.
You will usually get such a certificate from a certificate authority such as
Thawte or CAcert.
(In order to encrypt outgoing messages you don't need a personal digital ID, you
need the public certificate of the recipient instead.)
If the option
<A HREF="#smime-private-key-container"><EM>smime-private-key-container</EM></A>
is set then this option will have no effect.
<P>
Normally, Private Keys for use with S/MIME will be stored in the directory
which is the value of this option.
Those certificates will be stored in PEM format, one certificate per file.
The name of the file for the certificate corresponding to your
<P>
<CENTER><SAMP>emailaddress</SAMP></CENTER>
<P>
should be
<P>
<CENTER><SAMP>emailaddress.key</SAMP></CENTER>
<P>
For example, if your address is user@example.com the name of the file would be
<P>
<CENTER><SAMP>user@example.com.key</SAMP></CENTER>
<P>
in this directory.
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
Typically, the private key that you have will come from a Certificate
Authority.
The private key should be stored in a PEM format file that
looks something like:
<PRE>
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6

YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI
SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k
VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA
...
oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix
m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA==
-----END RSA PRIVATE KEY-----
</PRE>
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as &quot;S/MIME - Private Key Directory&quot;.
<P>

<DT> <A NAME="smime-private-key-container"><EM>smime-private-key-container</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
If this option is set it will be used instead of
<A HREF="#smime-private-key-directory"><EM>smime-private-key-directory</EM></A>.
<P>
This option gives you a way to store keys remotely on an IMAP server
instead of storing the keys one per file locally.
In order to do that you just give this option a remote folder name for a folder
which does not yet exist.
The name is similar to the name you might use for a remote configuration file.
A remote folder name might look something like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER>
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as &quot;S/MIME - Private Key Container&quot;.
<P>

<DT> <A NAME="smime-cacert-directory"><EM>smime-cacert-directory</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
If the option
<A HREF="#smime-cacert-container"><EM>smime-cacert-container</EM></A>
is set then this option will have no effect.
<P>
CACert is a shorthand name for certification authority certificate.
Normally <EM>Alpine</EM> will use the CACerts that are located in the standard system
location for CACerts.
It may be the case that one of your correspondents has a Digital ID which has
been signed by a certificate authority that is not in the regular set of system certificate
authorities.
You may supplement the system list by adding further certificates of your own.
These should  be stored in the directory
which is the value of this option.
The certificates will be stored in PEM format, one certificate per file.
The names of the files can be anything ending in &quot;.crt&quot;.
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
These PEM format CA certificates look very similar to your public
certificates for particular email addresses
(<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>).
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as &quot;S/MIME - Cert Authority Directory&quot;.
<P>

<DT> <A NAME="smime-cacert-container"><EM>smime-cacert-container</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
If this option is set it will be used instead of
<A HREF="#smime-cacert-directory"><EM>smime-cacert-directory</EM></A>.
<P>
This option gives you a way to store certificates remotely on an IMAP server
instead of storing the certificates one per file locally.
In order to do that you just give this option a remote folder name for a folder
which does not yet exist.
The name is similar to the name you might use for a remote configuration file.
A remote folder name might look something like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER>
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as &quot;S/MIME - Cert Authority Container&quot;.
<P>

<DT> <A NAME="smtp-server"><EM>smtp-server</EM></A>

<DD> One or more SMTP servers (host name or IP address) which <EM>Alpine</EM> will
use for outgoing mail.  If not set, <EM>Alpine</EM> passes outgoing email to the
<EM>sendmail</EM> program on the local machine.  <EM>PC-Alpine</EM> users must have
this variable set in order to send mail as they have no <EM>sendmail</EM>
program.
<P>
Your SMTP server may offer SMTP AUTH authentication.
It may even require it.
If your SMTP server offers SMTP AUTH authentication you may specify a
&quot;user&quot; name parameter to cause <EM>Alpine</EM> to attempt to authenticate.
This parameter requires an associated value,
the username identifier with which to establish the server
connection.
An example might be:

<P>
<CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER>
<P>

If AUTH authentication is offered by the server, this will cause <EM>Alpine</EM> to
attempt to use it.
If AUTH authentication is not offered by the server, this will cause <EM>Alpine</EM>
to fail sending with an error similar to:

<P>
<CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER>
<P>

Another type of authentication that is used by some ISPs is called
&quot;POP before SMTP&quot; or &quot;IMAP before SMTP&quot;,
which means that you have to authenticate
yourself to the POP or IMAP server by opening a mailbox before you
can send mail.
To do this, you usually only have to open your INBOX.
<P>
You may tell <EM>Alpine</EM> to use the
<A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A>
port (587) instead of the SMTP port (25) by including the &quot;submit&quot;
parameter
in this option.
At this time &quot;/submit&quot; is simply equivalent to specifying
port 587, though it may imply more than that at some point in the future.
Some ISPs are blocking port 25 in order to reduce the amount of spam
being sent to their users.
You may find that the submit option allows you to get around such a block.

<P>
<CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER>
<P>

To specify any non-standard port number on the SMTP server you may follow
the hostname with a colon followed by the portnumber.

<P>
<CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER>
<P>

Normally, when a connection is made to the Smtp-Server <EM>Alpine</EM> will attempt
to negotiate a secure (encrypted) session using Transport Layer Security (TLS).
If that fails then a non-encrypted connection will be attempted instead.
You may specify that a TLS connection is required if you wish.
If you append &quot;/tls&quot; to the name then the connection will fail
instead of falling back to a non-secure connection.

<P>
<CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER>
<P>

See the
<A HREF="config-notes.html#smtp-server">SMTP Servers</A>
section or the
<A HREF="config-notes.html#server-name-syntax">Server Name Syntax</A>
section for some more details.
<P>
This option is displayed as &quot;SMTP Server (for sending)&quot;.
<P>

<DT> <A NAME="sort-key"><EM>sort-key</EM></A>

<DD> This variable sets up the default Message Index sorting.
The default is to
sort by arrival order (the order the messages arrived in the folder).
It has the same functionality as the
<EM>-sort</EM> command line argument and the <EM>$</EM> command in the
"Folder Index".  If a <EM>sort-key</EM> is set, then all folders open during
the session will have that as the default sort order.  <P>

<DT> <A NAME="speller"><EM>speller</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
For <EM>PC-Alpine</EM>, you must install the aspell library code that you
may get from
<A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
<P>
This option affects the behavior of the <EM>^T</EM> (spell check)
command in the Composer.
It specifies the program invoked by <EM>^T</EM> in the Composer.
By default, <EM>Alpine</EM> uses the system's "spell" command.
<EM>Alpine</EM> will use the
command defined by this option (if any) instead.
When invoking the spell-checking program,
<EM>Alpine</EM> appends a tempfile name (where the message is passed)
to the command line.
<EM>Alpine</EM> expects the speller to correct the
spelling in that file. When you exit from the speller
program <EM>Alpine</EM> will read the
tmpfile back into the composer.
<P>
For Unix <EM>Alpine</EM> the program <EM>ispell</EM> works well as an
alternate spell checker.
If your Unix system has <EM>ispell</EM> it is probably reasonable to make
it the default speller by configuring it as the default in the
system configuration file, <CODE>/usr/local/lib/pine.conf</CODE>.

<P>
If this option is not set, then the system's <EM>spell</EM> command is used.
The spell command does not work the same as the alternate speller.
It produces a list of misspelled words on its standard output, instead,
and doesn't take a tempfile as an argument.
Don't set this speller option to the standard Unix spell command.
That won't work. If you want to use the standard Unix spell command,
set the speller option to nothing.

<DT> <A NAME="ssh-command"><EM>ssh-command</EM></A>

<DD> Sets the format of the command used to
open a UNIX secure shell connection. The default is
"%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
provided command. The first is for the command's pathname, the second is
for the host to connect to, the third is for the user to connect as, and
the fourth is for the connection method (typically <CODE>imap</CODE>).
<P>

<DT> <A NAME="ssh-open-timeout"><EM>ssh-open-timeout</EM></A>

<DD> Sets the time in seconds that <EM>Alpine</EM> will
attempt to open a UNIX secure shell connection.
The default is 15, the minimum non-zero value is 5,
and the maximum is unlimited. If this is set to zero ssh connections
will be completely disabled.
<P>

<DT> <A NAME="ssh-path"><EM>ssh-path</EM></A>

<DD> Sets the name of the command used to open a UNIX secure shell
connection. The default is typically <CODE>/usr/bin/ssh</CODE>.
<P>

<DT> <A NAME="standard-printer"><EM>standard-printer</EM></A>

<DD> System-wide configuration file only. Specifies a list of commands
for category 2 of the <EM>Setup/Printer</EM> screen, the standard print command
section. This is not used by <EM>PC-Alpine</EM>.
<P>

<DT> <A NAME="status-background-color"><EM>status-background-color</EM></A>
<DT> <A NAME="status-foreground-color"><EM>status-foreground-color</EM></A>

<DD> <A HREF="#status-color"><EM>Status Color</EM></A>.
<P>

<DT> <A NAME="status-message-delay"><EM>status-message-delay</EM></A>

<DD> This option has evolved over time, causing the possible values to be
counter-intuitive.
Read carefully before you set this option.
First we explain what the option does, then there is a longer discussion
following that.
<P>
If this is set to zero, the default value, it has <EM>no</EM> effect.
Positive and negative values serve two similar, but different purposes.
<P>
If it is set to a positive number, it causes the cursor to move to the
status line whenever a status message is printed and pause there for this
many seconds.
It will probably only be useful if the 
<A HREF="#show-cursor"><EM>show-cursor</EM></A>
feature is
also turned on.
Setting this option to a positive number can only be used to
<EM>increase</EM> the status message delay.
This may be useful for Braille displays, or other non-traditional displays.
<P>
If it is set to a negative number the interpretation is a bit complicated.
Negative numbers are used to <EM>decrease</EM> the amount of delay <EM>Alpine</EM> uses to
allow you to read important status messages.
Of course, this may cause you to miss some important messages.
If you see a message flash by but miss what it says you can use the
Journal command from the Main menu to read it.
If you set this option to a negative value, the delay will be
no more than one second less than the absolute value
of the value you set.
So if you set it to -1, the delay will be no more than zero seconds, no
delay at all.
If you set it to -2, the delay will be no more than 1 second.
And so on, -3 is 2 seconds, -4 is 3 seconds, ...
If the delay that <EM>Alpine</EM> would have used by default is less than this delay,
then the smaller delay set by <EM>Alpine</EM> will be used.
Setting this option to a negative value can only reduce the amount of
delay, never increase it.
<P>
Here is a more detailed explanation.
Status messages are the messages which show up spontaneously in the
status message line, the third line from the bottom of the screen.
By default, <EM>Alpine</EM> assigns each status message it produces a minimum
display time.
Some status messages have a minimum display time of zero.
You can see an example of such a message by paging up in this help text
until you reach the top of the screen.
If you try to page past the top you will see the message
<P>
<CENTER><SAMP>[Already at start of help text]</SAMP></CENTER>
<P>
in the status line.
If there is another more important use of the status message line this message
might be replaced quickly, or it even might not be shown at all.
However, if there is no reason to get rid of the message, it might stay
there for several seconds while you read the help.
An example where it is replaced immediately happens when you page up in
the help text past the top of the screen, but then type the &quot;WhereIs&quot;
command right after paging up.
The message will disappear immediately without causing a delay (unless you
have set this option to a positive value) to allow you to type input for
the &quot;WhereIs&quot; command.
Since it isn't a very important message, <EM>Alpine</EM> has set its minimum display
time to zero seconds.
<P>
Other messages have minimum display times of three or more seconds.
These are usually error messages that <EM>Alpine</EM> thinks you ought to see.
For example, it might be a message about a failed Save or a failed folder open.
It is often the case that this minimum display time won't delay you in
any way because the status message line is not needed for another reason.
However, there are times when <EM>Alpine</EM> has to delay what it is doing in
order to display a status message for the minimum display time.
This happens when a message is being displayed and <EM>Alpine</EM> wants to ask
for input from the keyboard.
For example, when you Save a message you use the status message line.
You get a prompt there asking for the name of the folder to save to.
If there is a status message being displayed that has not
yet displayed for its minimum
time <EM>Alpine</EM> will display that status message surrounded with the characters
&gt; and &lt; to show you that it is delaying.
That might happen, for example, if you tried to save to a folder that
caused an error, then followed that immediately with another Save command.
You might find yourself waiting for a status message like
<P>
<CENTER><SAMP>[&gt;Can't get write access to mailbox, access is readonly&lt;]</SAMP></CENTER>
<P>
to finish displaying for three seconds.
If that is something you find happening to you frequently, you may use
negative values of this option to decrease or eliminate that delay, at
the risk of missing the message.
<P>

<DT> <A NAME="stay-open-folders"><EM>stay-open-folders</EM></A>

<DD> This option affects low-level behavior of <EM>Alpine</EM>.
There is no default value for this option.
It is related to the options
<A HREF="#preopen-stayopen-folders">Preopen-Stayopen-Folders</A>,
<A HREF="#max-remote-connections">Max-Remote-Connections</A>,
and <A HREF="#offer-expunge-of-stayopen-folders">offer-expunge-of-Stayopen-Folders</A>.

<P>
Note: changes made to this list take effect the next time you open a
folder in the list.

<P>
This is a list of folders that will be permanently kept open once they
are first opened.
The names in this list may be either the nickname of an Incoming folder
or the full technical specification of a folder.
The folders in this list need not be remote IMAP folders, they could usefully
be local folders, as well.
If a folder in the list is a newsgroup or is not accessed either locally
or via IMAP, then the entry will be ignored.
For example, folders accessed via NNTP or POP3 will not be kept open, since
the way that new mail is found with those protocols involves closing and
reopening the connection.
<P>
Once a Stay Open folder has been opened, new-mail checking will continue
to happen on that folder for the rest of the <EM>Alpine</EM> session.
Your INBOX is always implicitly included in this Stay-Open list and doesn't
need to be added explicitly.
<P>
Another difference that you may notice between a Stay Open folder and a
non-Stay Open folder is which message is selected as the current message
when you enter the folder index.
Normally, the starting position for an incoming folder (which most Stay Open
folders will likely be) is controlled by the
<A HREF="#incoming-startup-rule"><EM>Incoming-Startup-Rule</EM></A>.
However, if a folder is a Stay Open folder, when you re-enter the folder
after the first time the current message will be the same as it was when
you left the folder.
An exception is made if you use the TAB command to get to the folder.
In that case, the message number will be incremented by one from what it
was when you left the folder.
<P>
The above special behavior is thought to be useful.
However, it is special and different from what you might at first expect.
The feature
<A HREF="#use-reg-start-rule"><EM>Use-Regular-Startup-Rule-for-Stayopen-Folders</EM></A>
may be used to turn off this special treatment.
<P>
If the message that was current when you left the folder no longer exists,
then the regular startup rule will be used instead.
<P>
This option is displayed as &quot;Stayopen Folders&quot;.
<P>

<DT> <A NAME="tcp-open-timeout"><EM>tcp-open-timeout</EM></A>

<DD> Sets the time in seconds that <EM>Alpine</EM> will
attempt to open a network connection. The default is 30, the minimum is 5,
and the maximum is system defined (typically 75). If a connection has not
completed within this many seconds <EM>Alpine</EM> will give up and consider it a
failed connection.
<P>

<DT> <A NAME="tcp-query-timeout"><EM>tcp-query-timeout</EM></A>

<DD> When <EM>Alpine</EM> times out a network read or write it will normally just display
a message saying &quot;Still waiting&quot;.
However, if enough time has elapsed since it started waiting it will offer
to let you break the connection.
That amount of time is set by this option, which defaults to 60 seconds,
has a minimum of 5 seconds, and a maximum of 1000 seconds.
<P>

<DT> <A NAME="tcp-read-warning-timeout"><EM>tcp-read-warning-timeout</EM></A>

<DD> Sets the time in seconds that <EM>Alpine</EM> will
wait for a network read before warning you that things are moving slowly
and possibly giving you the option to break the connection.
The default is 15 seconds. The minimum is 5 seconds and the maximumn is
1000 seconds.
<P>

<DT> <A NAME="tcp-write-warning-timeout"><EM>tcp-write-warning-timeout</EM></A>

<DD> Sets the time in seconds that <EM>Alpine</EM> will
wait for a network write before warning you that things are moving slowly
and possibly giving you the option to break the connection.
The default is 0 which means it is unset. If set to a non-zero value, the
minimum is 5 and the maximum is 1000.

<DT> <A NAME="threading-display-style"><EM>threading-display-style</EM></A>

<DD> When a folder is sorted by Threads or OrderedSubject,
this option will affect the MESSAGE INDEX display.
By default, <EM>Alpine</EM> will display the MESSAGE INDEX in the
&quot;show-thread-structure&quot; style if a folder is sorted
by Threads or OrderedSubject.
The possible values are:
<P>

<DL>
<DT><EM>none</EM></DT>
<DD>Regular index display.
The same index line as would be displayed without threading is used.
The only difference will be in the order of the messages.
</DD>

<DT><EM>show-thread-structure</EM></DT>
<DD>Threaded Subjects will be indented and vertical bars and horizontal
lines will be added to make it easier to see the relationships among
the messages in a thread (a conversation).
</DD>

<DT><EM>mutt-like</EM></DT>
<DD>This is the same as the option above except that the Subject
is suppressed (is blank) if it matches the previous Subject in the thread.
The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>.
Here is an example of what a mutt-like index might look like.
In this example, the first column represents the message number, the
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A>
is set to &quot;regular-index-with-expanded-threads&quot;, and the
<A HREF="#threading-lastreply-character"><EM>Threading-Lastreply-Character</EM></A>
is set to a backslash:
<PRE>
    1    Some topic
    2  . Subject           original message in thread
    3    |->               reply to 2
    4  . |->               another reply to 2
    5  . | &#92;->             reply to 4
    6  . |   &#92;->           reply to 5
    7    |     &#92;->         reply to 6
    8    |->               another reply to 2
    9  . |->New subject    another reply to 2 but with a New subject
   10    | |->             reply to 9
   11    | &#92;->             another reply to 9
   12    |   &#92;->           reply to 11
   13    &#92;->               final reply to 2
   14    Next topic
</PRE>
</DD>

<DT><EM>indent-subject-1</EM></DT>
<DD>Threaded Subjects will be indented one space per level of the conversation.
The bars and lines that show up in the show-thread-structure display will
not be there with this style.
</DD>

<DT><EM>indent-subject-2</EM></DT>
<DD>Same as above but indent two spaces per level instead of one space.
</DD>

<DT><EM>indent-from-1</EM></DT>
<DD>Similar to indent-subject-1, except that instead of indenting the
Subject field one space the From field of a thread will be indented one
space per level of the conversation.
</DD>

<DT><EM>indent-from-2</EM></DT>
<DD>Same as above but indent two spaces per level instead of one space.
</DD>

<DT><EM>show-structure-in-from</EM></DT>
<DD>The structure of the thread is illustrated with indenting, vertical bars,
and horizontal lines just like with the show-thread-structure option, but
the From field is used to show the relationships instead of the Subject field. 
</DD>

</DL>
<P>

<DT> <A NAME="threading-expanded-character"><EM>threading-expanded-character</EM></A>

<DD> The Threading-Expanded-Character option has a small effect on the MESSAGE
INDEX display when using a
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
other than <EM>none</EM>.
The value of this option is a single character.
This character is used to indicate that part of a thread has been expanded
and could be collapsed if desired with
the &quot;/&quot; Collapse/Expand command.
By default, the value of this option is a dot (.).
<P>
If this option is set to the Empty Value, then the column (and the following
blank column) will be deleted from the display.
<P>
This option is closely related to the
<A HREF="#threading-indicator-character"><EM>threading-indicator-character</EM></A>
option.
Another similar option which affects the thread display is the
<A HREF="#threading-lastreply-character"><EM>threading-lastreply-character</EM></A> option.

<DT> <A NAME="threading-index-style"><EM>threading-index-style</EM></A>

<DD> When a folder is sorted by Threads or OrderedSubject,
this option will affect the INDEX displays.
The possible values are:
<P>

<DL>
<DT><EM>regular-index-with-expanded-threads</EM></DT>
<DD>This is the default display.
If the configuration option
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
is set to something other than &quot;none&quot;, then this setting
will cause <EM>Alpine</EM> to start off with a MESSAGE INDEX with all of
the threads expanded.
That is, each message will have a line in the MESSAGE INDEX display.
The Collapse/Expand command (/) may be used to manually collapse or
expand a thread or subthread (see also <A HREF="#slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A>).
<P>
This setting affects the display when the folder is first threaded.
The collapsed state may also be re-initialized by re-sorting the folder manually
using the SortIndex command ($).
After re-sorting the threads will once again all be expanded, even if you
have previously collapsed some of them.
<P>
If &quot;threading-display-style&quot; is set to &quot;none&quot;, then
the display will be the regular default <EM>Alpine</EM> MESSAGE INDEX, but sorted
in a different order.
</DD>

<DT><EM>regular-index-with-collapsed-threads</EM></DT>
<DD>If the configuration option
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
is set to something other than &quot;none&quot;, then this setting
will cause <EM>Alpine</EM> to start out with all of the threads collapsed instead of
starting out with all of the threads expanded.
The Collapse/Expand command (/) may be used to manually collapse or
expand a thread or subthread (see also <A HREF="#slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A>).
<P>
This setting affects the display when the folder is first threaded.
The collapsed state may also be re-initialized by re-sorting the folder manually
using the SortIndex command ($).
After re-sorting the threads will once again all be collapsed, even if you
have previously expanded some of them.
</DD>

<DT><EM>separate-index-screen-always</EM></DT>
<DD>With this setting and the next, you will see an index of threads
instead of an
index of messages, provided you have sorted by Threads or OrderedSubject.
<P>
The THREAD INDEX contains a '*' in the first column if any message in the thread
is marked Important.
If not, it contains a '+' if any message in the thread is to you.
The second column is blank. The third column contains a 'D' if all of the
messages in the thread are deleted.
Otherwise, it contains an 'N' if any of the messages in the thread are New.
<P>
When you view a particular thread from the THREAD INDEX you will be
in the MESSAGE INDEX display
but the index will only contain messages from the thread you are viewing.
</DD>

<DT><EM>separate-index-screen-except-for-single-messages</EM></DT>
<DD>This is very similar to the option above.
When you are in the THREAD INDEX, one of the available commands
is &quot;ViewThd&quot;.
With the setting &quot;separate-index-screen-always&quot; (the option above)
when you view a particular thread you will be in the
MESSAGE INDEX display and the index will only contain messages from
the thread you are viewing.
If the thread you are viewing consists of a single message, the MESSAGE INDEX
will be an index with only one message in it.
If you use this &quot;separate-index-screen-except-for-single-messages&quot;
setting instead, then that index which contains a single message
will be skipped and you will go directly from the THREAD INDEX into the
MESSAGE TEXT screen.
</DD>

</DL>

<P>

<DT> <A NAME="threading-indicator-character"><EM>threading-indicator-character</EM></A>

<DD> The Threading-Indicator-Character option has a small effect on the MESSAGE
INDEX display when using a
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
other than <EM>none</EM> and sorting by Threads or OrderedSubject.
The value of this option is a single character.
This character is used to indicate that part of a thread (a conversation) is
hidden beneath a message.
The message could be expanded
if desired with the &quot;/&quot; Collapse/Expand command.
By default, the value of this option is the greater than sign (&gt;).
<P>
If this option is set to the Empty Value, then the column (and the following
blank column) will be deleted from the display.

<P>
This option is closely related to the
<A HREF="#threading-expanded-character"><EM>threading-expanded-character</EM></A>
option.
Another similar option which affects the thread display is the
<A HREF="#threading-lastreply-character"><EM>threading-lastreply-character</EM></A> option.
<P>

<DT> <A NAME="threading-lastreply-character"><EM>threading-lastreply-character</EM></A>

<DD>The Threading-Lastreply-Character option has a small effect on the MESSAGE
INDEX display when using a
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
of <EM>show-thread-structure</EM>, <EM>mutt-like</EM>, or
<EM>show-structure-in-from</EM>; and sorting by Threads or OrderedSubject.
The value of this option is a single character.
This character is used instead of the vertical line character when there are
no more replies directly to the parent of the current message.
It can be used to &quot;round-off&quot; the bottom of the vertical line
by setting it to a character such as a backslash (&#92;) or
a backquote (&#96;).
The default value of this option is the backslash character (&#92;).
This option may not be set to the Empty Value.
In that case, the default will be used instead.
<P>
This option is displayed as &quot;Threading Last Reply Character&quot;.
<P>

<DT> <A NAME="title-background-color"><EM>title-background-color</EM></A>
<DT> <A NAME="title-foreground-color"><EM>title-foreground-color</EM></A>

<DD> <A HREF="#title-color"><EM>Title Color</EM></A>.
<P>

<DT> <A NAME="title-closed-background-color"><EM>title-closed-background-color</EM></A>
<DT> <A NAME="title-closed-foreground-color"><EM>title-closed-foreground-color</EM></A>

<DD> <A HREF="#title-closed-color"><EM>Title-closed Color</EM></A>.
<P>

<DT> <A NAME="titlebar-color-style"><EM>titlebar-color-style</EM></A>

<DD> <A HREF="#titlebar-style"><EM>titlebar-color-style</EM></A>.
<P>

<DT> <A NAME="unknown-character-set"><EM>unknown-character-set</EM></A>

<DD> A text message should either be made up of all US-ASCII characters
or it should contain a charset label which tells the software which
character set encoding to use to interpret the message.
Sometimes a malformed message may be unlabeled but contain non-ascii text.
This message is outside of the standards so any attempt to read it could fail.
When <EM>Alpine</EM> attempts to read such a message it will try to interpret the
text in the character set you specify here.
For example, if you have correspondents who send you unlabeled messages that
are usually made up of characters from the WINDOWS-1251 character set, setting
this unknown-character-set to <CODE>WINDOWS-1251</CODE> will
allow you to read those messages.
Of course, if the unlabeled message is actually in some other character set,
then you may see garbage on your screen.

<P>
In the Setup/Config screen you may choose from a list of all the
character sets <EM>Alpine</EM> knows about by using the &quot;T&quot; ToCharsets command.
<P>

<DT> <A NAME="upload-command"><EM>upload-command</EM></A>

<DD> This option affects the behavior of the Composer's <EM>^R</EM> (Read File)
and <EM>^J</EM> (Attach File, in the header) commands.  It
specifies a Unix program name, and any necessary command line arguments,
that <EM>Alpine</EM> can use to transfer files from your personal computer into
messages that you are composing. <P>

<DT> <A NAME="upload-command-prefix"><EM>upload-command-prefix</EM></A>

<DD> This option is used in
conjunction with the <EM>upload-command</EM> option. 
It defines text to be written to the terminal emulator (via standard
output) immediately prior to starting the upload command. This is useful for
integrated serial line file transfer agents that permit command passing
(e.g., Kermit's APC method). <P>

<DT> <A NAME="url-viewers"><EM>url-viewers</EM></A>

<DD> List of programs to use to open Internet URLs.
This value affects <EM>Alpine</EM>'s handling of URLs that are found in the text of
messages you read. Normally, only URLs <EM>Alpine</EM> can handle directly are
automatically offered for selection in the "Message Text" screen. When
one or more comma delimited Web browsers capable of deciphering URLs on
their command line are added here, <EM>Alpine</EM> will choose the first available
browser to display URLs it doesn't recognize.
<P>

Additionally, to support various connection methods and browsers, each
entry in this list can begin with the special token
<CODE>_TEST(test-string)_</CODE>.
The <CODE>test-string</CODE> is a shell command that <EM>Alpine</EM>
will run and which must exit with a status of zero for <EM>Alpine</EM> to consider
that browser for use (the other criteria is that the browser must exist
as a full path or a path relative to your home directory).
<P>

Now for an example:

<BLOCKQUOTE>
    <CODE>
    url-viewers=_TEST("test -n '$&#123;DISPLAY}'")_  /usr/local/bin/netscape,
		/usr/local/bin/lynx,
		C:&#92;BIN&#92;NETSCAPE.BAT </CODE><BR>
</BLOCKQUOTE>

This example shows that for the first browser in the list to be used the
environment variable <CODE>DISPLAY</CODE> must be defined.
If it is, then the file <CODE>/usr/local/bin/netscape</CODE> must exist.
If either condition is not met, then the file
<CODE>/usr/local/bin/lynx</CODE> must exist.
If it doesn't, then the final path and file must
exist. Note that the last entry is a DOS/Windows path. This is one way
to support <EM>Alpine</EM> running on more than one architecture with the same
configuration file.
<P>

<DT> <A NAME="use-only"><EM>use-only-domain-name</EM></A>

<DD> Can be set to <EM>yes</EM> or <EM>no.</EM> Anything but
<EM>yes</EM> means <EM>no.</EM> If set to <EM>yes</EM> the first label in
the host name will be lopped off to get the domain name and the domain
name will be used for outgoing mail and such.  That is, if the host name
is <EM>carson.u.example.edu</EM> and this variable is set to <EM>yes,</EM>
then <EM>u.example.edu</EM> will be used on outgoing mail.  Only
meaningful if <A HREF="#user-domain"><EM>user-domain</EM></A> is NOT set.  <P>

<DT> <A NAME="user-domain"><EM>user-domain</EM></A>

<DD> Sets the domain or host name for the user, overriding the system host
or domain name.  See the <A HREF="config-notes.html#domain"><EM>domain name section</EM></A>.
The easiest way to change the full From address is with the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable.
<P>

<DT> <A NAME="user-id"><EM>user-id</EM></A>

<DD> <EM>PC-Alpine</EM> only and personal configuration file only.
Sets the username that is placed on all outgoing
messages. The username is the part of the address that comes before the "@".
The easiest way to change the full From address is with the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable.
<P>

<DT> <A NAME="user-input"><EM>user-input-timeout</EM></A>

<DD> If this is set to an integer greater than zero, then this is the number
of <EM>hours</EM> to wait for user input before <EM>Alpine</EM> times out.
If <EM>Alpine</EM> is
in the midst of composing a message or is waiting for user response to
a question, then it will not timeout.
However, if <EM>Alpine</EM> is sitting idle waiting for
the user to tell it what to do next and the user does not give any
input for this many hours, <EM>Alpine</EM> will exit.
No expunging or moving of read
messages will take place.
It will exit similarly to the way it would exit
if it received a hangup signal.
This may be useful for cleaning up unused <EM>Alpine</EM> sessions which have been
forgotten by their owners.
The <EM>Alpine</EM> developers envision system administrators
setting this to a value of several hours (24?) so that it won't surprise
a user who didn't want to be disconnected.
<P>

<DT> <A NAME="viewer-hdr-colors"><EM>viewer-hdr-colors</EM></A>

<DD> This variable holds the optional Header Colors and patterns which
have been defined by the user. This is usually modified by using
the <A HREF="#header-colors"><EM>Header Colors</EM></A> section
of the Setup Color screen.
<P>

<DT> <A NAME="viewer-hdrs"><EM>viewer-hdrs</EM></A>

<DD> You may change the default list of headers that are viewed by listing
the headers you want to view here.  If the headers in your <EM>viewer-hdrs</EM> 
list are present in the message, then they will be shown.  The order of
the headers you list will also be honored. If the special
value <EM>all-except</EM> 
is included as the first header in the <EM>viewer-hdrs</EM> list, then all
headers in the message except those in the list will be shown. The values
are all case insensitive.<P>
This option is displayed as &quot;Viewer Headers&quot;.
<P>
 
<DT> <A NAME="viewer-margin-left"><EM>viewer-margin-left</EM></A>

<DD> This variable controls the left-hand vertical margin's width in
<EM>Alpine</EM>'s Message Viewing screen.
Its value is the number of space characters preceding each displayed line.
For consistency with
<A HREF="#viewer-margin-right">Viewer-Margin-Right</A>,
you may specify the column number to start in
(column numbering begins with number 1)
instead of the width of the margin by appending a lower case letter
&quot;c&quot; to the number.
For example, a value of &quot;2c&quot; means to start the text in column two,
which is entirely equivalent to a value of &quot;1&quot;, which means to
leave a margin of 1 space.
<P>
The default is a left margin of 0 (zero).
Misconfigurations (for example, negative values or values with starting
left columns greater than the ending right column)
are silently ignored.
If the number of columns for text between the Viewer-Margin-Left and
the Viewer-Margin-Right is fewer than 8, then margins of zero will be used
instead.
<P>

<DT> <A NAME="viewer-margin-right"><EM>viewer-margin-right</EM></A>

<DD> This variable controls the right-hand vertical margin's width in
<EM>Alpine</EM>'s Message Viewing screen.
Its value is the number of space characters following each displayed line.
You may specify the column number to end the text in
(column numbering begins with number 1)
instead of the width of the margin by appending a lower case letter
&quot;c&quot; to the number.
For example, a value of &quot;76c&quot; means to end the text in column 76.
If the screen is 80 characters wide, this is equivalent to a value
of &quot;4&quot;, which means to leave a margin of 4 spaces.
However, if you use different size screens at different times, then these
two values are not equivalent.
<P>
The default right margin is 4.
Misconfigurations (for example, negative values or values with starting
left columns greater than the ending right column)
are silently ignored.
If the number of columns for text between the
<A HREF="#viewer-margin-left">Viewer-Margin-Left</A> and
the Viewer-Margin-Right is fewer than 8, then margins of zero will be used
instead.
<P>

<DT> <A NAME="overlap"><EM>viewer-overlap</EM></A>

<DD> This option specifies an aspect of <EM>Alpine</EM>'s Message Viewing screen. 
When the space bar is used to page forward in a message, the number of
lines specified by the <EM>viewer-overlap</EM> variable
will be repeated from the
bottom of the screen.  That is, if this was set to two lines, then the
bottom two lines of the screen would be repeated on the top of the next
screen. The normal default value is "2". <P>

<DT> <A NAME="window-position"><EM>window-position</EM></A>

<DD> Winsock version of <EM>PC-Alpine</EM> only.  Window position in the format: 
CxR+X+Yn Where C and R are the window size in characters and X and Y are
the screen position of the top left corner of the window.  <P>

</DL>

<HR>

<H2><A NAME="features-conf">Configuration Features</A></H2>

There are several features (options) which may be turned off or on.
The configuration variable
<A HREF="#feat-list"><EM>feature-list</EM></A> is a list of all the
features that are turned on or off.
If the name of a feature is in
the list it will be turned on.
If the name of a feature with the characters
<CODE>no-</CODE> prepended is in the list, it will turn the feature off.
This is useful for overriding system-wide defaults.
This is because, unlike all the other configuration variables,
the <EM>feature-list</EM> is additive.
That is, first the system-wide <EM>feature-list</EM> is read
and then the user's <EM>feature-list</EM> is read. This makes it possible
for the system manager to turn some of the features on by default while
still allowing the user to cancel that default.
For example, if the system manager has
turned on the <EM>allow-talk</EM> feature by default then a user may turn
it back off by including the feature <EM>no-allow-talk</EM> in his or her
personal configuration file. Of course, these details are usually handled
by <EM>Alpine</EM> when the user turns an option on or off from inside the
<EM>Setup/Config</EM> screen.
<P>

System managers should take some care when turning on features by default.
Some of the documentation assumes that all of the features are off by
default, so it could be confusing for a user if some are on by default instead.
Feature names are case-independent.
<P>

Here is an alphabetical list of possible features. 

<DL COMPACT>

<DT> <A NAME="allow-from"><EM>allow-changing-from</EM></A>

<DD> Prior to <EM>Pine</EM> 4.00 there was a <EM>compile</EM>-time option called
ALLOW_CHANGING_FROM. That has been replaced by a <EM>runtime</EM> feature.
If this feature is turned on then the From line can be changed just like
all the other header fields that can be changed. See the configuration
variables <A HREF="#cust-hdr"><EM>customized-hdrs</EM></A>
and <A HREF="#def-comp"><EM>default-composer-hdrs</EM></A>
for more information on editing headers.
<P>
The default value for this feature
is ON, so that editing of From headers is allowed
by default.
<P>

<DT> <A NAME="allow-talk"><EM>allow-talk</EM></A>

<DD> Unix <EM>Alpine</EM> only. By default, permission for
others to <EM>talk</EM> to your terminal is turned
off when you are running <EM>Alpine</EM>.  When this feature is set, permission is
instead turned on.
<P>

Note: The <EM>talk</EM> program has nothing to do with <EM>Alpine</EM> or email.  The 
<EM>talk</EM> daemon on your system will
attempt to print a message on your screen 
when someone else is trying to contact you.  If you wish to see these
messages while you are running <EM>Alpine</EM>, you should enable this feature.
<P>
 
If you do enable this feature and see a <EM>talk</EM> message, you must 
suspend or quit <EM>Alpine</EM> before you can respond.
<P>

<DT> <A NAME="alternate-compose-menu"><EM>alternate-compose-menu</EM></A>

<DD>This feature controls the menu that is displayed when Compose is selected.
If set, a list of options will be presented, with each option representing
the type of composition that could be used. This feature is most useful for
users who want to avoid being prompted with each option separately, or who
want to avoid the checking of remote postponed or form letter folders.
The possible types of composition are:

<P>
New, for starting a new composition. Note that if New is selected and roles
are set, roles are checked for matches and applied according to the setting
of the matching role.

<P>
Interrupted, for continuing an interrupted composition. This option is only
offered if an interrupted message folder is detected.

<P>
Postponed, for continuing postponed compositions. This option is offered
if a postponed-folder is set in the config <EM>REGARDLESS OF</EM> whether or not
the postponed folder actually exists. This option is especially handy
for avoiding having to check for the existence of a remote postponed folder.

<P>
Form, for using form letters. This option is offered if the form-letter-folder
is set in the config, and is not checked for existence for reasons similar
to those explained by the postponed option.

<P>
setRole, for selecting a role to apply to a composition.

<P>

<DT> <A NAME="alternate-role-menu"><EM>alternate-role-menu</EM></A>

<DD> Normally the Role Command allows you to choose
a role and compose a new message using that role.
When this feature is set, the role command will first ask whether you want to
Compose a new message, Forward the current message, Reply to the
current message, or Bounce the current message.
If you are not in the MESSAGE INDEX and are not viewing a message,
then there is no current message and the question will be skipped.
After you have chosen to Compose, Forward, Reply or Bounce you will
then choose the role to be used.
<P>
When Bouncing the &quot;Set From&quot; address is used for the
Resent-From header, the &quot;Set Fcc&quot; value is used for the Fcc
provided that the option
<A HREF="#fcc-on-bounce">&quot;Fcc-On-Bounce&quot;</A> is turned on,
and the &quot;Use SMTP Server&quot; value is used for the SMTP server, if
set.
Other actions of the role are ignored when Bouncing.
<P>
This feature is displayed as &quot;Alternate Role (#) Menu&quot;.
<P>


<DT> <A NAME="assume-slow-link"><EM>assume-slow-link</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature affects <EM>Alpine</EM>'s display routines.  If set, the normal
inverse-video cursor (used to highlight the current item in a list) will be
replaced by an <EM>arrow</EM> cursor and other screen update optimizations for
low-speed links (e.g. 2400 bps dialup connections) will be activated.
One of the optimizations is that colored index lines (set up with Indexcolor
Rules) will not be colored.
This might be useful if <I>you</I> know you have a slow speed link but for some
reason <EM>Alpine</EM> doesn't know.
<P>

<DT> <A NAME="auto-read-msg"><EM>auto-move-read-msgs</EM></A>

<DD> This feature controls an aspect
of <EM>Alpine</EM>'s behavior upon quitting.  If set,
and the <A HREF="#read-msg-fold"><EM>read-message-folder</EM></A>
variable is also set, then <EM>Alpine</EM> will
automatically transfer all read messages from the <EM>INBOX</EM> to
the designated folder and mark
them as deleted in the <EM>INBOX</EM>.  Messages in the <EM>INBOX</EM> marked
with an <EM>N</EM> (meaning New, or unseen) are not affected.
<P>
This feature is displayed as &quot;Auto Move Read Messages&quot;.
<P>

<DT> <A NAME="auto-open-next-unread"><EM>auto-open-next-unread</EM></A>

<DD> This feature controls the behavior of the TAB key when traversing folders
in the optional <A HREF="#inc-fold"><EM>incoming-folders</EM></A>
collection or in optional <A HREF="#news-coll"><EM>news-collections</EM></A>.
<P>

When the TAB (Next New) key is pressed, and there are no more unseen
messages in the current (incoming message or news) folder, <EM>Alpine</EM> will
search the list of folders in the current collection for one containing
New or Recent (new since the last time the folder was opened) messages.
This behavior may be modified slightly with the
<A HREF="#tab-uses-unseen-for-next-folder">Tab-Uses-Unseen-For-Next-Folder</A>
feature which causes <EM>Alpine</EM> to look for Unseen messages instead of Recent
messages.
By default, when such a folder is found,
<EM>Alpine</EM> will ask whether you wish to
open the folder.
If this feature is set, <EM>Alpine</EM> will automatically open the
folder without prompting.
<P>

<DT> <A NAME="auto-unselect-after-apply"><EM>auto-unselect-after-apply</EM></A>

<DD> This feature affects the behavior of the Apply command.  If set,
the Apply command will do the operation you specify, but then will
implicitly do an &quot;UnSelect All&quot;, so that you will automatically be back in
the normal Index view after the Apply. 
<P>

<DT> <A NAME="auto-unzoom-after-apply"><EM>auto-unzoom-after-apply</EM></A>

<DD> If set, and if
you are currently looking at a Zoomed Index view of selected messages,
the <EM>Apply</EM> command will do the operation you specify, but then will
implicitly do an <EM>UnZoom</EM>, so that you will automatically be back in
the normal Index view after the <EM>Apply</EM>.
This feature is set by default.
<P>

<DT> <A NAME="auto-zoom-after-select"><EM>auto-zoom-after-select</EM></A>

<DD> If set, the <EM>; select</EM> command will automatically
perform a <EM>Zoom</EM> after the <EM>select</EM> is complete.
This feature is set by default.
<P>

<DT> <A NAME="busy-cue-spinner-only"><EM>busy-cue-spinner-only</EM></A>

<DD> When <EM>Alpine</EM> is delayed for some reason it usually shows that
something is happening with a small animated display in the status
message line near the bottom of the screen.
Setting this feature will cause that animation to be the same
each time instead of having <EM>Alpine</EM> choose a random animation.
You may turn the animation off altogether by setting the
<A HREF="#busy-cue-rate"><EM>busy-cue-rate</EM></A>
option to zero.
<P>

<DT> <A NAME="check-newmail-when-quitting"><EM>check-newmail-when-quitting</EM></A>

<DD> If set, <EM>Alpine</EM> will check for new mail after you give the
Quit command.
If new mail has arrived since the previous check, you will be notified
and given the choice of quitting or not quitting.
<P>

<DT> <A NAME="combined-addrbook-display"><EM>combined-addrbook-display</EM></A>

<DD> This feature affects the address book display screens.
Normally, expanding an address book from the ADDRESS BOOK LIST screen
will cause the remaining address books and directory servers to disappear
from the screen, leaving only the entries of the expanded address book.
If this feature is set, then the other address books will remain on the screen,
so that all of the address books can be present at once.

<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the entries in the
current address book, not all of the entries in all of the address books.
The WhereIs command will change a little.
It will search through all of the text on the screen plus all of the entries
from expanded address books.

<P>
When this feature is set, the setting of the feature
<A HREF="#expanded-view-of-addressbooks"><EM>expanded-view-of-addressbooks</EM></A>
has an effect.
<P>
This feature is displayed as &quot;Combined Addressbook Display&quot;.
<P>

<DT> <A NAME="combined-folder-display"><EM>combined-folder-display</EM></A>

<DD> This feature affects the folder list display screens.
Normally, each folder list is viewed within its collection only.  This
command allows folder lists to be viewed within a single screen that
combines the contents of all collections.

<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the folders in the
current collection, not all of the entries in all of the collections.
The WhereIs command will change a little.
It will search through all of the folders in the current collection as well
as all the folder in any other expanded collection.

<P>
When this feature is set, the setting of the feature
<A HREF="#expanded-view-of-folders"><EM>expanded-view-of-folders</EM></A>
has an effect.
<P>

<DT> <A NAME="combined-subdirectory-display"><EM>combined-subdirectory-display</EM></A>

<DD> This feature affects the Folder List screen when
the
<A HREF="#combined-folder-display"><EM>combined-folder-display</EM></A>
feature is enabled.  Normally, selecting a directory from the Folder
List takes you into a new screen displaying only the contents of
that directory.

<P>
Enabling this feature will cause the contents of the selected
directory to be
displayed within the boundaries of the
<A HREF="background.html#collections"><EM>Collection</EM></A>
it is a part of.  All previously displayed collections will remain
in the screen.

<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the folders in the
directory, as opposed to all of the entries in all of the collections.
The WhereIs command will change a little.
It will search through all of the folders in the current collection as well
as all the folder in any other expanded collection.

<P>

<DT> <A NAME="compose-cancel-confirm-uses-yes"><EM>compose-cancel-confirm-uses-yes</EM></A>

<DD> This feature affects what happens when you type ^C to cancel a composition.
By default, if you attempt to cancel a composition by typing ^C, you will be
asked to confirm the cancellation by typing a &quot;C&quot;
for <EM>C</EM>onfirm.
It logically ought to be a &quot;Y&quot; for <EM>Y</EM>es, but that is
risky because the &quot;^C Y&quot; needed to cancel a message
is close (on the keyboard) to the &quot;^X Y&quot; needed to send a message.
<P>
If this feature is set the confirmation asked for
will be a &quot;<EM>Y</EM>es&quot;
instead of a &quot;<EM>C</EM>onfirm&quot; response.
<P>

<DT> <A NAME="compose-cut-from-cursor"><EM>compose-cut-from-cursor</EM></A>

<DD> If set, the <EM>^K</EM> command in the composer will cut from the
current cursor position to the end of the line,
rather than cutting the entire line.
<P>
This feature is displayed as &quot;Ctrl-K Cuts From Cursor&quot;.
<P>

<DT> <A NAME="compose-maps-delete-key-to-ctrl-d"><EM>compose-maps-delete-key-to-ctrl-d</EM></A>

<DD> If set, Delete will be equivalent to ^D, and delete
the current character. Normally <EM>Alpine</EM> defines the Delete key
to be equivalent to ^H, which deletes the <EM>previous</EM>
character.
<P>
This feature is displayed as &quot;Delete Key Maps to Ctrl-D&quot;.
<P>

<DT> <A NAME="compose-rejects-unqualified-addrs"><EM>compose-rejects-unqualified-addrs</EM></A>

<DD> If set, unqualified names entered as addresses will be treated as errors
unless they match an addressbook nickname or are looked up successfully
on an LDAP server. <EM>Alpine</EM> will not attempt to turn
them into complete addresses by adding your local domain (which <EM>Alpine</EM> normally
does by default).
<P>

A complete (fully-qualified) address is one containing a username
followed by an <EM>@</EM> symbol, followed by a host or domain name (e.g.
<EM>jsmith@example.com</EM>). An unqualified name is one without the
<EM>@</EM> symbol
and host or domain name (e.g. <EM>jsmith</EM>).
<P>
This feature is displayed as &quot;Compose Rejects Unqualified Addresses&quot;.
<P>

<DT> <A NAME="compose-send-offers-first-filter"><EM>compose-send-offers-first-filter</EM></A>

<DD> If you have <A HREF="#sending-filters"><EM>sending-filters</EM></A>
configured, setting this feature will cause the first filter in the
<EM>sending-filters</EM> list to be offered as the default
instead of <EM>unfiltered</EM>, the usual default.
<P>

<DT> <A NAME="compose-sets-newsgroup-without-confirm"><EM>compose-sets-newsgroup-without-confirm</EM></A>

<DD> If you enter the
composer while reading a newsgroup, you will normally be prompted to
determine whether you intend the new message to be posted to the current
newsgroup or not.  If this feature is set, <EM>Alpine</EM> will not prompt you
in this situation, and will assume that you do indeed wish to post
to the newsgroup you are reading.
<P>
This feature is displayed as &quot;Compose Sets Newsgroup Without Confirming&quot;.
<P>

<DT> <A NAME="confirm-role-even-for-default"><EM>confirm-role-even-for-default</EM></A>

<DD> If you have roles, when you Reply to or Forward a message, or Compose
a new message, <EM>Alpine</EM>
will search through your roles for one which matches.
Normally, if no matches are found you will be placed into the composer
with no opportunity to select a role.
If this feature is set, then you will be asked to confirm that you don't
want a role.
This will give you the opportunity to select a role (with the ^T command).
If you confirm no role with a Return, you will be placed in
the composer with no role.
You may also confirm with either an &quot;N&quot; or a &quot;Y&quot;.
These behave the same as if you pressed the Return.
(The &quot;N&quot; and &quot;Y&quot; answers are available because they
match what you might type if there was a role match.)
<P>
If you are using the alternate form of the Compose command called
&quot;Role&quot;, then all of your roles will be available to you,
independent of the value of this feature and of the values set for all of
Reply Use, Forward Use, and Compose Use.
<P>

<DT> <A NAME="continue-tab-without-confirm"><EM>continue-tab-without-confirm</EM></A>

<DD> Normally, when you use the TAB NextNew
command and there is a problem checking a folder, you are asked
whether you want to continue with the search in the following folder or not.
This gives you a chance to stop the NextNew processing.
<P>
If this feature is set you will not be asked.
It will be assumed that you want to continue.
<P>
This feature is displayed as &quot;Continue NextNew Without Confirming&quot;.
<P>

<DT> <A NAME="convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>

<DD> Normally, the message dates that you see in the
MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from.
For example, if a message was sent to you from a few timezones to the east
it might appear that it was sent from the future;
or if it was sent from somewhere to the west it might appear
as if it is from yesterday even though it was sent only a few minutes ago.
If this feature is set an attempt will be made to convert the dates
to your local timezone to be displayed.
<P>
Note that this does not affect the results of Select by Date or of
anything else other than these displayed dates.
When viewing the message you may look at the original unconverted value of the Date
header by using the HdrMode Command.
<P>

<DT> <A NAME="copy-to-to-from"><EM>copy-to-address-to-from-if-it-is-us</EM></A>

<DD> This feature affects the From address used when Replying to a message.
It is probably only useful if you have some
<A HREF="#alt-addresses">alt-addresses</A>
defined.
When enabled, it checks to see if any of the addresses in the To or Cc
fields of the message you are replying to is one of your addresses.
If it is, and there is only one of them, then that address is used as
the From address in the message you are composing.
In other words, you will be using a From address that is the same
as the To address that was used to get the mail to you in the first place.

<P>
If a role is being used and it has a From address defined, that From address will
be used rather than the one derived from this feature.
<P>

<DT> <A NAME="delete-skips-deleted"><EM>delete-skips-deleted</EM></A>

<DD> If set, this
feature will cause the <EM>Delete</EM> command to
advance past other messages that
are marked deleted.  In other words, pressing <EM>D</EM> will both mark the
current message deleted and advance to the next message that is not marked
deleted.
This feature is set by default.
<P>

<DT> <A NAME="disable-config-cmd"><EM>disable-config-cmd</EM></A>

<DD> If set, the configuration
screen <EM>Setup/Config</EM> will not be available at all.
<P>

<DT> <A NAME="disable-save-input-history"><EM>disable-save-input-history</EM></A>

<DD> Many of the prompts that ask for input in the status line near the
bottom of the screen will respond to Up Arrow and Down Arrow
with the history of previous entries.
For example, in the MESSAGE INDEX screen when you use the WhereIs
command the text you entered will be remembered and can be recalled
by using the Up Arrow key.
Another example, when saving a message the folders saved to will
be remembered and can be recalled using the arrow keys.
<P>
In the Save prompt, some users prefer that the Up and Down arrow keys
be used for the Previous Collection and Next Collection commands
instead of for a history of previous saves.
If this option is set the Up and Down arrow keys will become synonyms for the
Previous Collection and Next Collection (^P and ^N) commands in the
prompt for the name of a folder to Save to or in the prompt for the
name of a folder to GoTo.
When this feature is not set (the default), ^P and ^N will change the
collection and the arrow keys will show the history.
<P>

<DT> <A NAME="disable-kblock"><EM>disable-keyboard-lock-cmd</EM></A>

<DD> In the Main <EM>Alpine</EM> menu there is a Keyboard locking
command (<EM>KBLock</EM>). If this feature is set, that command won't be
available to the user.
<P>

<DT> <A NAME="disable-keymenu"><EM>disable-keymenu</EM></A>

<DD> If set, the command key menu that normally appears on the
bottom two lines of the screen will not usually be there. Asking for
help with <EM>^G</EM> or <EM>?</EM> will cause the key menu to
appear instead of causing the help message to come up. If you want to
actually see the help text,
another <EM>^G</EM> or <EM>?</EM> will show it to you.
After the key menu has popped
up with the help key it will remain there for an <EM>O Other</EM> command but
will disappear if any other command is typed.
<P>

<DT> <A NAME="disable-password-caching"><EM>disable-password-caching</EM></A>
<P>

<DD> Normally, loginname/password combinations are cached in <EM>Alpine</EM>
so that the user does not have to enter the same password more than once
in a session.
A disadvantage to this approach is that the password must be stored in
the memory image of the running <EM>Alpine</EM> in order that it can be reused.
In the event that <EM>Alpine</EM> crashes and produces a core dump, and that core
dump is readable by others, the loginname and password could possibly be read
from the core dump.
<P>
If this feature is set, then the passwords will not be cached and
the user will have to retype the password whenever <EM>Alpine</EM> needs it.
Even with this feature set there is still some chance that the core
file will contain a password, so care should be taken to make the
core files unreadable.
<P>
NOTE: If PASSFILE caching is enabled, this does not disable it.
That is a separate and independent feature.
<P>

<DT> <A NAME="disable-password-cmd"><EM>disable-password-cmd</EM></A>

<DD> If set the <EM>Newpassword</EM> command usually available under the
<EM>Setup</EM> command will not be available.
<P>

<DT> <A NAME="disable-pipes-in-sigs"><EM>disable-pipes-in-sigs</EM></A>

<DD> If set it will be an error to append a vertical bar (|) to the name
of a signature file.
Appending a vertical bar normally causes the signature file to be executed
to produce the signature.
<P>

<DT> <A NAME="disable-pipes-in-templates"><EM>disable-pipes-in-templates</EM></A>

<DD> If set it will be an error to append a vertical bar (|) to the name
of a template file.
Appending a vertical bar normally causes the signature file to be executed
to produce the signature.
<P>

<DT> <A NAME="disable-regex"><EM>disable-regular-expression-matching-for-alternate-addresses</EM></A>

<DD> Normally, the
<A HREF="#alt-addresses">alt-addresses</A>
option is interpreted as a regular expression.
One type of address that might cause trouble is an address that
contains a plus sign.
If you want to have an address with a plus as one of your
alternate addresses
and you don't want to use regular expressions, then setting this
feature will cause <EM>Alpine</EM> to treat the addresses you list literally instead.
<P>

<DT> <A NAME="disable-roles-setup-cmd"><EM>disable-roles-setup-cmd</EM></A>

<DD> If set the <EM>Roles</EM> command usually available under the
<EM>Setup</EM> command will not be available.
<P>

<DT> <A NAME="disable-roles-sig-edit"><EM>disable-roles-sig-edit</EM></A>

<DD> If set the roles editor in the <EM>Setup/Roles</EM> command will not allow
editing of signature files with the F subcommand.
<P>

<DT> <A NAME="disable-roles-template-edit"><EM>disable-roles-template-edit</EM></A>

<DD> If set the roles editor in the <EM>Setup/Roles</EM> command will not allow
editing of template files with the F subcommand.
<P>

<DT> <A NAME="disable-sender"><EM>disable-sender</EM></A>

<DD> If set, <EM>Alpine</EM> will not generate a &quot;Sender:&quot; or &quot;X-X-Sender&quot; header.
This may be desirable on a system which is virtually hosting many domains,
and the sysadmin has other methods available for tracking a message to
its originator.
<P>
This feature is displayed as &quot;Do Not Generate Sender Header&quot;.
<P>

<DT> <A NAME="disable-setlocale-collate"><EM>disable-setlocale-collate</EM></A>

<DD> This is a hard to understand feature that should only be used in rare cases.
Normally, the C function call
<P>
<CENTER><SAMP>setlocale(LC_COLLATE, &quot;&quot;)</SAMP></CENTER>
<P>
is used by <EM>Alpine</EM>.
If you want to try turning it off,
setting this feature will turn it off.
This part of the locale has to do with the sort order
of characters in your locale.
<P>

<DT> <A NAME="disable-shared-namespaces"><EM>disable-shared-namespaces</EM></A>

<DD> If this hidden feature is set
the automatic search for namespaces &quot;ftp&quot;,
&quot;imapshared&quot;, and &quot;imappublic&quot; by the underlying library
will be disabled.
The reason this feature exists is because there are some implementations
of system password lookup routines which are very slow when presented with
a long loginname which does not exist.
This feature could be set to prevent the delay at startup time when the
names above are searched for in the password file.
<P>

<DT> <A NAME="disable-signature-edit-cmd"><EM>disable-signature-edit-cmd</EM></A>

<DD> If set the <EM>Signature</EM> editing command usually available under the
<EM>Setup</EM> command will not be available.
<P>

<DT> <A NAME="disable-take-fullname"><EM>disable-take-fullname-in-addresses</EM></A>

<DD> Normally, when TakeAddr is used to copy an address or addresses
from a message into an address book entry, <EM>Alpine</EM> will try to preserve
the full name associated with each address in the list of addresses.
The reason for this is so that if the entry is a list or later becomes a
list, then information about the individual addresses in the list
is preserved.
If you would rather just have the simple addresses in the list of addresses,
set this feature. For example, with the default setting you might
see something like this in the ADDRESS BOOK editor after you type TakeAddr
<P>
<PRE>
 Nickname  : nick
 Fullname  : Bedrock Elders
 Fcc       :
 Comment   :
 Addresses : Fred Flintstone &lt;flint@bedrock.org&gt;,
             Barney Rubble &lt;rubble@bedrock.org&gt;
</PRE>
<P>
but with this feature set it would look like
<P>
<PRE>
 Nickname  : nick
 Fullname  : Bedrock Elders
 Fcc       :
 Comment   :
 Addresses : flint@bedrock.org,
             rubble@bedrock.org
</PRE>
<P>
instead. Note the difference in the Addresses field.
<P>

<DT> <A NAME="disable-take-last-comma-first"><EM>disable-take-last-comma-first</EM></A>

<DD> Normally, when <EM>TakeAddr</EM> is used to copy an address
from a message into an address book, <EM>Alpine</EM> will attempt to rewrite the
full name of the address in the form:
 
<BLOCKQUOTE>
	Last, First <BR>
</BLOCKQUOTE>
	 
instead of
	  
<BLOCKQUOTE>
	First Last <BR>
</BLOCKQUOTE>
		  
It does this because many people find it useful to sort by Last name instead
of First name. If this feature is set, then the <EM>TakeAddr</EM> command will
not attempt to reverse the name in this manner.
<P>

<DT> <A NAME="disable-terminal-reset-for-display-filters"><EM>disable-terminal-reset-for-display-filters</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature affects <EM>Alpine</EM>'s behavior when using
<A HREF="#display-filters"><EM>Display-Filters</EM></A>.
Normally, before the display filter is run, the terminal mode is reset
to what it was before you started <EM>Alpine</EM>.
This may be necessary if the filter requires the use of the terminal.
For example, it may need to interact with you.
If you set this feature, then the terminal mode will not be reset.
One thing that turning on this feature should fix is the coloring of
quoted text in the message view, which
breaks because the terminal reset resets the color state of the terminal
(<A HREF="#color-config">Color Configuration</A>).
<P>

<DT> <A NAME="downgrade-multipart-to-text"><EM>downgrade-multipart-to-text</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when sending mail.  Internet
standards require <EM>Alpine</EM> to translate all non-ASCII characters in
messages that it sends using MIME encoding.  This encoding can be
ostensibly broken for recipients if any agent between <EM>Alpine</EM> and the
recipient, such as an email list expander, appends text to the
message, such as list information or advertising.  When sending such
messages <EM>Alpine</EM> attempts to protect such encoding by placing extra
MIME boundaries around the message text.
<P>
These extra boundaries are invisible to recipients that 
use MIME-aware email programs (the vast majority).  However, if
you correspond with users of email programs that are not MIME-aware,
or do not handle the extra boundaries gracefully, you can
use this feature to prevent <EM>Alpine</EM> from including the extra
MIME information.  Of course, it will increase the likelihood
that non-ASCII text you send may appear corrupt to the recipient.
<P>

<DT> <A NAME="enable-8bit-esmtp-negotiation"><EM>enable-8bit-esmtp-negotiation</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when sending mail.
By default, this feature is set.
Internet standards
require that all electronic mail messages traversing the global Internet
consist of 7bit ASCII characters unless a pair of cooperating mail 
transfer agents explicitly agree to allow 8bit messages.  In general, 
then, exchanging messages in non-ASCII characters requires MIME encoding.
<P>
 
However, there are now Internet standards that allow for unencoded 8bit
exchange of messages between cooperating systems.  When this feature is set
<EM>Alpine</EM> will try to negotiate unencoded 8bit transmission during the
sending process.  Should the negotiation fail, <EM>Alpine</EM> will fall back to its
ordinary encoding rules. 
<P>

Note, this feature relies on your system's mail transport agent or
configured <A HREF="#smtp-server"><EM>smtp-server</EM></A>
having the negotiation mechanism introduced in
"Extended SMTP" (ESMTP) and the specific extension called <EM>8BITMIME</EM>. 
<P>

<DT> <A NAME="enable-8bit-nntp-posting"><EM>enable-8bit-nntp-posting</EM></A>

<DD> The Internet standard for exchanging USENET news messages (RFC-1036)
specifies that USENET messages should conform to Internet mail standards
and contain only 7bit characters, but much of the news transport software
in use today is capable of successfully sending messages containing 8bit
characters.  Hence, many people believe that it is appropriate to send 8bit
news messages without any MIME encoding.
<P>

Moreover, there is no Internet standard for explicitly negotiating 8bit
transfer, as there is for Internet email.  Therefore, <EM>Alpine</EM> provides the
option of posting unencoded 8bit news messages, though not as the default.
Setting this feature will turn OFF <EM>Alpine</EM>'s MIME encoding of newsgroup
postings that contain 8bit characters. 
<P>

Note, articles may cross a path or pass through news transport software
that is unsafe or even hostile to 8bit characters.  At best this will only
cause the posting to become garbled.  The safest way to transmit 8bit
characters is to leave <EM>Alpine</EM>'s MIME encoding turned on, but recipients
who lack MIME-aware tools are often annoyed when they receive MIME-encoded 
messages.
<P>

<DT> <A NAME="enable-aggregate-command-set"><EM>enable-aggregate-command-set</EM></A>

<DD> When this feature is set you may use the commands and subcommands that relate to
performing operations on more than one message at a time.
We call these "aggregate operations".
In particular, the <EM>; Select</EM>, <EM>A Apply</EM>, and
<EM>Z Zoom</EM> commands are enabled by this feature.
<EM>Select</EM> is used to <EM>tag</EM> one
or more messages meeting the specified criteria. <EM>Apply</EM> can then be used
to apply any message command to all of the selected/tagged messages.
Further, the <EM>Zoom</EM> command allows you to toggle the "Folder Index" view
between just those Selected and all messages in the folder.
<P>

This feature also enables the <EM>^X</EM> subcommand in
the "Folder Index" <EM>WhereIs</EM>
command which causes
all messages matching the <EM>WhereIs</EM> argument to become
selected.
<P>

You may also use aggregate operations in the address book screens where
you are operating on address book entries instead of on messages.
<P>

<DT> <A NAME="enable-alt-ed"><EM>enable-alternate-editor-cmd</EM></A>

<DD> If this feature is set (the default), and the <A HREF="#editor"><EM>editor</EM></A>
variable is not set, entering
the <EM>^_</EM> (Control-underscore) key while
composing a message will prompt you
for the name of the editor you would like to use.
<P>
 
If the environment variable <CODE>$EDITOR</CODE> is set,
this value will be offered as a default.
  
If the <EM>editor</EM> variable is set, the <EM>^_</EM> key will activate
the specified editor without prompting, in which case it is not necessary to
set the <EM>enable-alternate-editor-cmd</EM> feature.
This feature is not available in <EM>PC-Alpine</EM>.
<P>
This feature is displayed as &quot;Enable Alternate Editor Command&quot;.
<P>

<DT> <A NAME="enable-alt-imp"><EM>enable-alternate-editor-implicitly</EM></A>

<DD> If this feature and the <A HREF="#editor"><EM>editor</EM></A>
variable are both set, <EM>Alpine</EM> will
automatically activate the specified editor when the cursor is moved from
the header of the message being composed into the message text.  For
replies, the alternate editor will be activated immediately.  If this
feature is set but the <EM>editor</EM> variable is not set,
then <EM>Alpine</EM> will
automatically ask for the name of an alternate editor when the cursor
is moved out of the headers, or if a reply is being done.
This feature is not available in <EM>PC-Alpine</EM>.
<P>

<DT> <A NAME="enable-arrow-navigation"><EM>enable-arrow-navigation</EM></A>

<DD> This feature controls the behavior of the left and right arrow keys.
If set, the left and right arrow keys will operate like the usual
navigation keys <EM>&lt;</EM> and <EM>&gt;</EM>.
This feature is set by default.

<P>
If you set this feature, and do not like the changed behavior of the up/down 
arrow keys when navigating through the FOLDER LIST screen -- 
<B>first</B> from column to column, if more than one folder is 
displayed per row, 
and <B>then</B> from row to row -- you may either also wish to set the feature 
<A HREF="#enable-arrow-navigation-relaxed"><EM>enable-arrow-navigation-relaxed</EM></A>, 
<A HREF="#single-column-folder-list"><EM>single-column-folder-list</EM></A>,
or use the ^P/^N (instead of up/down arrow) keys to move up/down the list of 
folders in each column.
<P>

<DT> <A NAME="enable-arrow-navigation-relaxed"><EM>enable-arrow-navigation-relaxed</EM></A>

<DD> This feature controls the behavior of the left and right arrow keys
in the FOLDER LIST screen when the 
<A HREF="#enable-arrow-navigation"><EM>enable-arrow-navigation</EM></A>
feature is set.
This feature is set by default.
<P>

When this feature is set, the left and right
arrow keys in the FOLDER LIST screen
move the highlight bar to the left or right, and the up and
down arrows move it up or down.

<P>
When the &quot;Enable-Arrow-Navigation&quot; feature is set and this
feature is not set;
the left and right arrow keys in the Folder List screen strictly
track the commands bound to the '&lt;' and '&gt;' keys, and the up
and down arrow keys move the highlight bar to the previous and next
folder or directory name.

<P>

<DT> <A NAME="enable-background-sending"><EM>enable-background-sending</EM></A>

<DD> If set, this
feature enables a subcommand in the composer's <EM>Send?</EM> confirmation
prompt.  The subcommand allows you to tell <EM>Alpine</EM> to handle the actual
posting in the background.  While this feature usually allows posting
to appear to happen very fast, it has no affect on the actual delivery
time it takes a message to arrive at its destination.
<P>

This feature isn't supported on all systems.  All DOS and Windows,
as well as several Unix ports, do not recognize this feature.
It is not possible to use background sending if the feature
<A HREF="#send-without-confirm">send-without-confirm</A> is set.
<P>

Error handling is significantly different when this feature is
enabled.  Any message posting failure results in the message
being appended to your <EM>Interrupted</EM> mail folder.  When you
type the <EM>Compose</EM> command, <EM>Alpine</EM> will notice this folder and
offer to extract any messages contained.  Upon continuing a 
failed message, <EM>Alpine</EM> will display the nature of the failure 
in the status message line.
<P>

Under extreme conditions, it is possible for message data to
get lost.  Do not enable this feature if you typically run close
to any sort of disk-space limits or quotas.
<P>

<DT> <A NAME="enable-bounce-cmd"><EM>enable-bounce-cmd</EM></A>

<DD> Setting this feature enables the <EM>B Bounce</EM> command,
which will prompt
for an address and <EM>remail</EM> the message to the new recipient.
This command
is used to re-direct messages that you have received in error, or need to
be redirected for some other reason (e.g. list moderation).  The final
recipient will see a header indicating that you have Resent the msg, but
the message's From: header will show the original author of the message,
and replies to it will go back to that author, and not to you.
<P>
This feature is displayed as &quot;Enable Bounce Command&quot;.
<P>

<DT> <A NAME="enable-cruise-mode"><EM>enable-cruise-mode</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when you hit the "Space Bar" at
the end of a displayed message.  Typically, <EM>Alpine</EM> complains that the end
of the text has already been reached.  Setting this feature causes such
keystrokes to be interpreted as if the <EM>Tab</EM> key had been hit, thus
taking you to the next <EM>interesting</EM> message, or scanning ahead to the 
next incoming folder with <EM>interesting</EM> messages.
<P>

<DT> <A NAME="enable-cruise-mode-delete"><EM>enable-cruise-mode-delete</EM></A>

<DD> This feature modifies the behavior of <EM>Alpine</EM>'s <EM>enable-cruise-mode</EM>
feature. Setting this feature causes <EM>Alpine</EM> to implicitly delete read
messages when it moves on to display the next <EM>interesting</EM> message.
<P>

NOTE: Beware when enabling this feature <B>and</B> the
<A HREF="#expunge-wo-confirm"><EM>expunge-without-confirm</EM></A> feature.
<P>
This feature is displayed as &quot;Enable Cruise Mode With Deleting&quot;.
<P>

<DT> <A NAME="enable-delivery-status-notification"><EM>enable-delivery-status-notification</EM></A>

<DD> If set, this
feature enables a subcommand in the composer's "Send?" confirmation
prompt.  The subcommand allows you to tell <EM>Alpine</EM> to request the type of
Delivery Status Notification (DSN) which you would like.  Most users will
be happy with the default, and need not enable this feature. See the online
help for more details.
<P>
It is not possible to use delivery status notifications if the feature
<A HREF="#send-without-confirm">send-without-confirm</A> is set.
<P>

Note that this is not a method to request <EM>READ</EM> receipts, which tells
the sender when the receiver has read the message. In this case we're talking
about notification of delivery to the mailbox, not notification that the
message has been seen.
<P>

<DT> <A NAME="enable-dot-files"><EM>enable-dot-files</EM></A>

<DD> If set, files beginning with dot (".") will be
visible in the file browser.  For example, you'll be able to select them
when using the browser to add an attachment to a message.
<P>

<DT> <A NAME="enable-dot-folders"><EM>enable-dot-folders</EM></A>

<DD> If set, folders beginning with dot (".") may be added
and viewed.
This feature is displayed as &quot;Enable Hidden Folders&quot;.
<P>

<DT> <A NAME="enable-exit-via-lessthan-command"><EM>enable-exit-via-lessthan-command</EM></A>

<DD> If set, then on screens where there is an <EM>Exit</EM> command
but no <EM>&lt;</EM> command, the <EM>&lt;</EM> key will perform
the same function as the <EM>Exit</EM> command.
This feature is set by default.
<P>

<DT> <A NAME="enable-fast-recent-test"><EM>enable-fast-recent-test</EM></A>

<DD> This feature controls the behavior of the TAB key when traversing folders
in the optional 
<A HREF="#enable-incoming-folders">Incoming-Folders</A>
collection or in optional News-Collections.

<P>
When the TAB
(NextNew)
key is pressed, the default behavior is to
explicitly examine the status of the folder for the number of recent
messages (messages delivered since the last time it was viewed).
Depending on the size and number of messages in the folder, this test
can be time consuming.

<P>
Enabling this feature will cause <EM>Alpine</EM> to only test for the existence of
any recent messages rather than to obtain the count.  This is much faster
in many cases.  The downside is that you're not given the number of recent
messages when prompted to view the next folder.
If the feature
<A HREF="#tab-uses-unseen-for-next-folder">Tab-Uses-Unseen-For-Next-Folder</A>
is turned on, then the present feature will have no effect.
<P>

<DT> <A NAME="enable-flag-cmd"><EM>enable-flag-cmd</EM></A>

<DD> Setting this feature enables the <EM>* Flag</EM> command,
which allows you to
manipulate the status flags associated with a message.
By default, <EM>Flag</EM>
will set the <EM>Important</EM> flag, which results in an asterisk being
displayed in column one of the "Folder Index" for such messages.
<P>
This feature is displayed as &quot;Enable Flag Command&quot;.
<P>

<DT> <A NAME="enable-flag-screen-implicitly"><EM>enable-flag-screen-implicitly</EM></A>

<DD> This feature modifies the behavior of the <EM>* Flag</EM> command
(provided it too is enabled).
By default, when the <EM>* Flag</EM> command is selected,
<EM>Alpine</EM> offers a prompt to set one of several flags and also offers the
option of entering the detailed flag manipulation screen via the <EM>^T</EM>
key. Enabling this feature causes <EM>Alpine</EM> to immediately enter the detailed
flag screen rather than first offer the simple prompt.
The
<A HREF="#enable-flag-screen-keyword-shortcut">Enable-Flag-Screen-Keyword-Shortcut</A> option offers a slightly different way of setting keywords.
<P>

<DT> <A NAME="enable-flag-screen-keyword-shortcut"><EM>enable-flag-screen-keyword-shortcut</EM></A>

<DD> This feature modifies the behavior of the
Flag command and the Select command.
By default, when the "* Flag" command is selected,
<EM>Alpine</EM> offers a prompt to set one of several flags and also offers the
option of entering the detailed flag manipulation screen via the "^T"
key.
If you have
<A HREF="#keywords">keywords</A>
defined, then enabling this feature adds a shortcut way to set or unset
keywords.
You use &quot;*&quot; followed by the first letter of a keyword (or the nickname of
a keyword if you've given it a nickname) and that will set the keyword.
<P>
An example is easier to understand than the explanation.
The flag command can always be used to set the system flags.
For example, to set the Answered flag you would type
<P>
<CENTER><SAMP>* A</SAMP></CENTER>
<P>
Now suppose you have defined a keyword &quot;Work&quot; using the Keywords
option in the Config screen.
By default, to set a keyword like &quot;Work&quot; you would usually
have to go to the Flag Details screen using
the &quot;^T To Flag Details&quot; command.
Instead, if you have enabled this feature, you may type
<P>
<CENTER><SAMP>* W</SAMP></CENTER>
<P>
to set the Work flag, or
<P>
<CENTER><SAMP>* ! W</SAMP></CENTER>
<P>
to unset it.
Just like for the other flag setting commands, the case of the letter does
not matter, so &quot;w&quot; or &quot;W&quot; both set the &quot;Work&quot;
keyword.
<P>
Notice that you can only use this trick for one keyword that begins
with &quot;W&quot;.
If you happen to have a &quot;Work&quot; keyword and another keyword that is
&quot;WIFI&quot; the &quot;* W&quot; command will set the first one in
your list of keywords.
Also, there are five letters which are reserved for system
flags and the NOT command.
If you type &quot;* A&quot; it will always set the Answered flag, not
your &quot;Aardvark&quot; keyword.
In order to set the &quot;Aardvark&quot; keyword you'll still have to use
the Flag Details screen.
<P>
Because enabling the
<A HREF="#enable-flag-screen-implicitly">Enable-Flag-Screen-Implicitly</A>
option causes <EM>Alpine</EM> to skip directly to the Flag Details screen when the
Flag command is used, 
setting it will cause this feature to have no effect at all.
<P>
Similarly, when Selecting by Keyword, setting this option will allow you
to use Keyword initials instead of full keywords.
<P>

<DT> <A NAME="enable-full-header-cmd"><EM>enable-full-header-cmd</EM></A>

<DD> This feature enables the <EM>H Full Headers</EM> command which
toggles between
the display of all headers in the message and the normal edited view of
headers. The <EM>Full Header</EM> command also controls
which headers are included
for <EM>Export</EM>, <EM>Pipe</EM>, <EM>Print</EM>, <EM>Forward</EM>,
and <EM>Reply</EM> functions. (For <EM>Reply</EM>, the
<EM>Full Header</EM> mode will respect
the <EM>include-headers-in-reply</EM> feature setting.)
<P>
If Full Header mode is turned on and you Forward a message, you will
be asked if you'd like to forward the message as an attachment, as opposed
to including the text of the message in the body of your new message.
<P>
If you have also turned on the
<A HREF="#quote-suppression-threshold">&quot;Quote Suppression&quot;</A>
option then the Full Headers command actually rotates through three states
instead of just two.
The first is the normal view with long quotes suppressed.
The second is the normal view but with the long quotes included.
The last enables the display of all headers in the message.
When using Export, Pipe, Print, Forward, or Reply the quotes are
never suppressed, so the first two states are identical.
<P>
Normally, the Header Mode will reset
to the default behavior when moving to a new message.
The mode can be made to persist from message to message by setting the feature
<A HREF="#quell-full-header-auto-reset">Quell-Full-Header-Auto-Reset</A>.
<P>
This feature is displayed as &quot;Enable Full Header Command&quot;.
<P>

<DT> <A NAME="enable-full-header-and-text"><EM>enable-full-header-and-text</EM></A>

<DD>
<P>This feature affects how the <EM>H Full Headers</EM> command displays
message text.  If set, the raw message text will be displayed.  This
especially affects MIME formatted email, where the entire MIME format
will be displayed.  This feature similarly affects how messages are
included for the <EM>Export</EM>, <EM>Pipe</EM>, <EM>Print</EM>, <EM>Forward</EM>, 
and <EM>Reply</EM> functions.

<DT> <A NAME="enable-goto-in-file-browser"><EM>enable-goto-in-file-browser</EM></A>

<DD> Setting this causes <EM>Alpine</EM> to offer the <EM>G Goto</EM> command in
the file browser. The Goto command allows you to explicitly type in the
desired directory.
That is the default.
<P>

<DT> <A NAME="enable-incoming-folders"><EM>enable-incoming-folders</EM></A>

<DD> If set, this feature defines a pseudo-folder collection called
<EM>INCOMING MESSAGE FOLDERS</EM>.
Initially, the only folder included in this collection
will be your <EM>INBOX</EM>, which will no longer show up in your default
saved-message folder collection.
<P>
This feature is displayed as &quot;Enable Incoming Folders Collection&quot;.
<P>

<DT> <A NAME="enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>

<DD> This feature is only operational if you have enabled the optional
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
If you do have Incoming Message Folders and you also set this feature,
then the number of Unseen messages in each folder will be displayed
in the FOLDER LIST screen for the Incoming Message Folders.
The number of Unseen messages in a folder will be displayed in parentheses
to the right of the name of each folder.
If there are no Unseen messages in a folder then only the name
is displayed, not a set of parentheses with zero inside them.
A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for
the Incoming Message Folders to cause an immediate update.
<P>
If a check for Unseen messages fails for a particular folder then Alpine
will no longer attempt to check that folder for the duration of the
session and this will be indicated by a question mark inside the
parentheses.
<P>
The features
<A HREF="#incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A>,
<A HREF="#incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A>,
<A HREF="#incoming-check-list"><EM>incoming-check-list</EM></A>,
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A>,
<A HREF="#incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A>, and
<A HREF="#incoming-check-timeout"><EM>incoming-check-timeout</EM></A>
all affect how this feature behaves.
<P>

<DT> <A NAME="disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A>

<DD> This feature affects the display of dates in the MESSAGE INDEX.
Normally an attempt is made to localize the dates
used in the MESSAGE INDEX display to your locale.
This is controlled with the
LC_TIME locale setting on a UNIX system.
On Windows the Regional Options control panel may be used to set the date format.
At the programming level, <EM>Alpine</EM> is using the strftime routine
to print the parts of a date.
<P>
If this feature is set, dates are displayed in English and
with the conventions of the United States.
<P>

<DT> <A NAME="enable-jump-shortcut"><EM>enable-jump-shortcut</EM></A>

<DD> When this feature is set you may enter a number (followed by RETURN)
and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
screens. In other words, it obviates the need for typing the <EM>J</EM> for the
<EM>Jump</EM> command.
<P>

<DT> <A NAME="enable-lame-list-mode"><EM>enable-lame-list-mode</EM></A>

<DD> This feature modifies the method <EM>Alpine</EM> uses to ask your IMAP
server for folder names to display in the the FOLDER LIST screen.
It is intended to compensate for a small set of IMAP servers that
are programmed to ignore a part of the request, and thus respond
to <EM>Alpine</EM>'s query with nonsensical results.
<P>

If you find that <EM>Alpine</EM> is erroneously displaying blank folder lists,
try enabling this feature.
<P>

NOTE: Enabling this feature has consequences for the Goto and Save
commands.  Many servers allow access to folders outside the area
reserved for your personal folders via some reserved character,
typically '#' (sharp), '~' (tilde) or '/' (slash).  This mechanism
allows, at the Goto and Save prompts, quick access to folders
outside your personal folder collection without requiring a specific
collection definition.  This behavior will generally not be available
when this feature is enabled.
<P>
This feature is displayed as &quot;Compensate for Deficient IMAP servers&quot;.
<P>

<DT> <A NAME="enable-mail-check-cue"><EM>enable-mail-check-cue</EM></A>

<DD> If set, this will cause an asterisk to appear in the upper
left-hand corner of the screen whenever <EM>Alpine</EM> checks for new mail, and two
asterisks whenever <EM>Alpine</EM> saves (checkpoints) the state of the current
mailbox to disk.
<P>

<DT> <A NAME="enable-mailcap-param-substitution"><EM>enable-mailcap-param-substitution</EM></A>

<DD> If set, this will allow mailcap named parameter substitution to occur
in mailcap entries.
By default, this is turned off to prevent security problems which may occur
with some incorrect mailcap configurations.
For more information, RFC1524 and look for "named parameters" in the
text of the RFC.
<P>
This feature is displayed as &quot;Enable Mailcap Parameter Substitution&quot;.
<P>

<DT> <A NAME="enable-mouse-in-xterm"><EM>enable-mouse-in-xterm</EM></A>

<DD>
This feature controls whether or not an X terminal mouse can be used with
<EM>Alpine</EM>.  If set, and the $DISPLAY variable indicates that an X terminal is
being used, the left mouse button on the mouse can be used to select text
or commands.
Clicking on a command at the bottom of the screen will behave as if you had
typed that command.
Clicking on an index line will move the current message highlight to
that line.
Double-clicking on an index line will view the message.
Double-clicking on a link will view the link.
<P>
This type of mouse support will also work in some terminal emulators which are
not actually X terminals, but which have extra code to support the xterm
style mouse.
For those emulators you not only need to turn this feature on but you also
have to set the $DISPLAY environment variable even though it isn't needed
for your terminal.
That will cause <EM>Alpine</EM> to think that it is an xterm and to properly interpret the
escape sequences sent by the mouse.
<P>
Note: if this feature is set, the behavior of X terminal cut-and-paste is
also modified.  It is sometimes possible to hold the shift key down while clicking
left or middle mouse buttons for the normal xterm cut/paste operations. 
There is also an <EM>Alpine</EM> command to toggle this mode on or off.
The command is Ctrl-&#92; (Control-backslash).
<P>

<DT> <A NAME="enable-msg-view-addresses"><EM>enable-msg-view-addresses</EM></A>

<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen.
Setting this feature causes <EM>Alpine</EM> to select possible email addresses
from the displayed text and display them in boldface for selection.
<P>

The first available email address is displayed in inverse.  This is the
"selected" address.
Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to enter the message
composition screen with the To field filled in with the selected address.
<P>

Use the up and down arrow keys to change which of the addresses
displayed in boldface is the current selection.
<P>
This feature is displayed as &quot;Enable Message View Address Links&quot;.
<P>

<DT> <A NAME="enable-msg-view-attachments"><EM>enable-msg-view-attachments</EM></A>

<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen.
Setting this feature causes <EM>Alpine</EM> to present attachments in boldface.
The first available attachment is displayed in inverse.  This is the
"selected" attachment.  Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display
the selected attachment.  Use the up and down arrow keys to change which of the
attachments displayed in boldface is the current selection.
<P>
 
Speaking of arrow keys, the Up and Down Arrows will select the next
and previous attachments if one is available on the screen for selection.
Otherwise, they will simply adjust the viewed text one line up or down.
<P>
  
Similarly, when selectable items are present in a message, the Ctrl-F
key can be used to select the next item in the message independent
of which portion of the viewed message is currently displayed. The
Ctrl-B key can be used to select the previous item in the same way.
<P>
This feature is displayed as &quot;Enable Message View Attachment Links&quot;.
<P>

<DT> <A NAME="enable-msg-view-forced-arrows"><EM>enable-msg-view-forced-arrows</EM></A>

<DD> This feature modifies Up and Down arrow key behavior in <EM>Alpine</EM>'s
"Message Text" screen when selectable Attachments, URL's, or
web-hostnames are presented. <EM>Alpine</EM>'s usual behavior is to move to
the next or previous selectable item if currently displayed or
simply to adjust the screen view by one line if the next selectable line
is off the screen.
<P>
 
Setting this feature causes the Up and Down arrow keys to behave as
if no selectable items were present in the message.
<P>
  
Note, the <EM>Ctrl-F</EM> (next selectable item) and
<EM>Ctrl-B</EM> (previous selectable item) functionality is unchanged.
<P>
This feature is displayed as &quot;Enable Message View Forced Arrows&quot;.
<P>

<DT> <A NAME="enable-msg-view-urls"><EM>enable-msg-view-urls</EM></A>

<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen.
When this feature is set (the default) <EM>Alpine</EM> will select possible URLs from the
displayed text and display them in boldface for selection.
<P>

The first available URL is displayed in inverse.  This is the
"selected" URL.  Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display
the selected URL via either built-in means as with <CODE>mailto:</CODE>,
<CODE>imap:</CODE>, <CODE>news:</CODE>, and <CODE>nntp:</CODE>,
or via an external application as defined
by the <A HREF="#url-viewers"><EM>url-viewers</EM></A> variable.
<P>

Use the up and down arrow keys to change which of the URLs displayed in boldface
is the current selection.
<P>
This feature is displayed as &quot;Enable Message View URL Links&quot;.
<P>

<DT> <A NAME="enable-msg-view-web-hostnames"><EM>enable-msg-view-web-hostnames</EM></A>

<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen.
When this feature is set (the default) <EM>Alpine</EM> will select possible web hostnames
from the displayed text and display them in boldface for selection.
<P>

The first available hostname is displayed in inverse.  This is the
"selected" hostname.  Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display
the selected hostname via an external application as defined
by the <A HREF="#url-viewers"><EM>url-viewers</EM></A> variable.
<P>

Use the up and down arrow keys to change which of the hostnames displayed in
boldface is the current selection.
<P>
This feature is displayed as &quot;Enable Message View Web Hostname Links&quot;.
<P>

<DT> <A NAME="enable-multiple-newsrcs"><EM>enable-multiple-newsrcs</EM></A>

<DD> This feature makes it so <EM>Alpine</EM> can use multiple newsrcs based on
the news server being connected to, which allows for separate lists
of subscribed-to newsgroups. When this feature is not set, there is only
one list of newsgroups.
<P>
Under this feature, the name of a newsrc is based on the news server.
For example, if your <a href="#newsrc-path">newsrc-path</a>
is set to &quot;.newsrc&quot;, and the news server you are connecting to is
news.example.com, then the newsrc to be used is .newsrc-news.example.com.
Setting this feature for the first time will allow for the option of using
your old newsrc the next time you read news.
<P>
If this feature is set, then the feature
<A HREF="#mult-newsrc-hostnames-as-typed">Mult-Newsrc-Hostnames-As-Typed</A>
also may affect the name of the newsrc file that is used.

<P>

<DT> <A NAME="enable-newmail-in-xterm-icon"><EM>enable-newmail-in-xterm-icon</EM></A>

<DD> This feature controls whether or not <EM>Alpine</EM> will attempt to announce new
mail arrival when it is running in an X terminal window and that window
is iconified.
If set, and the <CODE>$DISPLAY</CODE> variable indicates that an X
terminal is being used, <EM>Alpine</EM> will send appropriate escape sequences to
the X terminal to modify the label on <EM>Alpine</EM>'s icon to indicate that new
mail has arrived. <EM>Alpine</EM> will also modify the <EM>Alpine</EM> window's title to
indicate new mail.
See also <A HREF="#enable-newmail-short-text-in-icon">Enable-Newmail-Short-Text-in-Icon</A>.
<P>

<DT> <A NAME="enable-newmail-short-text-in-icon"><EM>enable-newmail-short-text-in-icon</EM></A>

<DD> This feature controls the text to be displayed in an icon in the event
of a new message arrival.  Normally, the message will
be the one that is displayed on the screen.  This feature shortens the
message to a count of the number of new messages in brackets.  This may be
more useful for those who use the window's title bar in the task bar as a
new mail indicator.  This feature is only useful if the
<A HREF="#enable-newmail-in-xterm-icon">Enable-Newmail-in-Xterm-Icon</A>
is also set.  Like the Enable-Newmail-in-Xterm-Icon
feature, this feature is only relevant when run in an xterm environment.
<P>

<DT> <A NAME="enable-partial-match-lists"><EM>enable-partial-match-lists</EM></A>

<DD> This feature affects the subcommands available when <EM>Sav</EM>ing
or Opening a new folder. If set, the subcommand <EM>^X ListMatches</EM> will be
available. This command allows you to type in a substring of the folder
you are looking for and when you type <EM>^X</EM> it will display all folders
which contain that substring in their names.
This feature is set by default.
<P>

<DT> <A NAME="enable-print-via-y-command"><EM>enable-print-via-y-command</EM></A>

<DD> By default, <EM>Alpine</EM>'s print command is available by pressing the <EM>%</EM>
key. In older versions of <EM>Pine</EM>, the print command was accessed by
pressing the <EM>Y</EM> key.
<P>
 
Enabling this feature will cause <EM>Alpine</EM> to recognize both the old
command, <EM>Y</EM>, and the new <EM>%</EM> method for invoking
printing.  Note, key menu labels are not changed as a result of
enabling this feature.
<P>

<DT> <A NAME="enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A>

<DD> This feature affects the Reply command's &quot;Include original message
in Reply?&quot; prompt.  When enabled, it causes the
&quot;Edit Indent String&quot; sub-command to appear which allows 
you to edit the string <EM>Alpine</EM> would otherwise use to denote included 
text from the message being replied to.<P>

Thus, you can change <EM>Alpine</EM>'s default message quote character (usually
an angle bracket) on a per message basis. So you could change your quoted message to
look, for example, like this:<p>
 
<pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
 
John: I just wanted to say hello and to congratulate you
John: on a job well done!</pre><p>

The configuration option
<A HREF="#reply-ind-str">&quot;reply-indent-string&quot;</A>
may be used to change what appears as the default string to be edited.
<P>
NOTE: Edited reply-indent-strings only apply to the message
currently being replied to.
<P>

<DT> <A NAME="enable-rules-under-take"><EM>enable-rules-under-take</EM></A>

<DD> Normally, the Take command takes addresses from a message and helps you
put them into your Address Book.
If you use Rules for Indexcolors, Roles, Filtering, or Scoring;
you may find it useful
to be able to Take information from a message's headers and put it into
a new Rule.
When this feature is set, you will be given an extra prompt which gives
you the choice to Take into the Address Book or Take into a rule.
<P>
This feature is displayed as &quot;Enable Take Rules&quot;.
<P>

<DT> <A NAME="enable-search-and-replace"><EM>enable-search-and-replace</EM></A>

<DD> If set <EM>Alpine</EM>'s composer offers the <EM>R Replace</EM> command
option inside the <EM>W WhereIs</EM> command.
<P>

<DT> <A NAME="enable-sigdashes"><EM>enable-sigdashes</EM></A>

<DD> If set and a <EM>signature-file</EM> exists, the line consisting of
the three characters "<CODE>-- </CODE>" (dash dash space) is included
before the signature.
This only happens if the signature doesn't already contain such a line.
<P>
In addition, when you Reply or Followup to a message containing one of
these special lines and choose to include its text, <EM>Alpine</EM> will observe
the convention of not including text beyond the special line in your
reply.
<P>

<DT> <A NAME="enable-suspend"><EM>enable-suspend</EM></A>

<DD> Setting this feature will allow you to type <EM>^Z</EM>
and temporarily suspend <EM>Alpine</EM>. Not available on <EM>PC-Alpine</EM>.
<P>

<DT> <A NAME="enable-tab-completion"><EM>enable-tab-completion</EM></A>

<DD> This feature enables the <EM>TAB</EM> key when
at a prompt for a filename. In this
case, <EM>TAB</EM> will cause the
partial name already entered to be automatically
completed, provided the partial name is unambiguous.
This feature is set by default.
<P>
Similarly, this feature also enables TAB completion of address book
nicknames when at a prompt for a nickname,
or when typing in an address field in the composer.
<P>

<DT> <A NAME="enable-take-export"><EM>enable-take-export</EM></A>

<DD> Normally, the Take command takes addresses from a message and helps you
put them into your Address Book.
When this feature is set, you will be given an extra prompt which gives you
the choice to Take addresses into a file instead of your Address
Book.
Only the user@domain_name part of the address is put in the file.
<P>

<DT> <A NAME="enable-tray-icon"><EM>enable-tray-icon</EM></A>

<DD> <EM>PC-Alpine</EM> only. This option restores a behavior of 
previous versions of PC-Alpine.  These
versions, when started, installed a PC-Alpine icon in the notification 
tray of Window's Taskbar.  The primary use of this icon was to indicate
new mail arrival by turning red (while the Taskbar icon remained green).
Additionally, the icon now changes to yellow to signify that a mail folder
has been closed unexpectedly.
<P>
Rather than add another icon to the Taskbar, this version of PC-Alpine will 
color its Taskbar entry's icon red (as well as the icon in the Window
Title).  This feature is only provided for backwards compatibility.
<P>

<DT> <A NAME="enable-unix-pipe-cmd"><EM>enable-unix-pipe-cmd</EM></A>

<DD> This feature enables the <EM>| Pipe</EM> command
that sends the current message
to the specified Unix command for external processing.
<P>
This feature is displayed as &quot;Enable Unix Pipe Command&quot;.
<P>

<DT> <A NAME="enable-verbose-smtp-posting"><EM>enable-verbose-smtp-posting</EM></A>

<DD> This feature controls an aspect of <EM>Alpine</EM>'s message sending.  When enabled,
<EM>Alpine</EM> will send a <CODE>VERB</CODE> (i.e., VERBose) command
early in the posting process
intended to cause the server SMTP to provide a more detailed account of
the transaction.  This feature is typically only useful to system
administrators and other support personnel as an aid in troubleshooting
problems.
 
Note, this feature relies on a specific capability of the system's mail
transport agent or configured <A HREF="#smtp-server"><EM>smtp-server</EM></A>.
<P>

<DT> <A NAME="expanded-view-of-addressbooks"><EM>expanded-view-of-addressbooks</EM></A>

<DD> If multiple address books (either personal or global) are defined, and you
wish to have them all expanded implicitly upon entering the ADDRESS BOOK
screen, then set this feature. This feature will have no effect unless the
feature
<A HREF="#combined-addrbook-display"><EM>combined-addrbook-display</EM></A>
is also set.
<P>

<DT> <A NAME="expanded-view-of-distribution-lists"><EM>expanded-view-of-distribution-lists</EM></A>

<DD> If this feature is set, then distribution lists in the address book
screen will always be expanded automatically.
<P>

<DT> <A NAME="expanded-view-of-folders"><EM>expanded-view-of-folders</EM></A>

<DD> If multiple folder collections are defined, and you
wish to have them all expanded implicitly upon entering the FOLDER LIST
screen, then set this feature. This feature will have no effect unless the
feature
<A HREF="#combined-folder-display"><EM>combined-folder-display</EM></A>
is also set.
<P>

<DT> <A NAME="expose-hidden-config"><EM>expose-hidden-config</EM></A>

<DD> The purpose of this feature is to allow you to change configuration
features and variables which are normally hidden.
This is particularly useful if you are using a remote configuration file,
where it is difficult to edit the file manually, but it may also be used
on a local pinerc configuration file.
<P>
If set, most configuration variables and features which are normally
hidden from view will show up in the Setup/Configuration screen.
They will be at the bottom of the configuration screen.
You can find them by searching for the word &quot;hidden&quot;.
<P>

Note that this is an advanced feature which should be used with care.
The reason that this part of the configuration is normally hidden is because
there is a significant potential for causing problems if you change these
variables.
If something breaks after a change try changing it back to see if that is
what is causing the problem.
There are also some variables which are normally hidden because they are
manipulated through <EM>Alpine</EM> in other ways.
For example, the &quot;address-book&quot; variable is normally set using
the Setup/AddressBooks screen, so there is little reason to edit it directly.
The &quot;incoming-folders&quot; variable is normally changed by using
the Add, Delete, and Rename commands in the FOLDER LIST screen,
and the &quot;last-time-prune-questioned&quot; variable is normally used
internally by <EM>Alpine</EM> and not set directly by the user.
<P>

<DT> <A NAME="expunge-only-manually"><EM>expunge-only-manually</EM></A>

<DD> Normally, when you close a folder which contains deleted messages you are
asked if you want to expunge those messages from the folder permanently.
If this feature is set, you won't be asked and the deleted messages will
remain in the folder.
If you choose to set this feature you will have to expunge the
messages manually using the eXpunge command, which you can use while
in the MESSAGE INDEX screen.
If you do not expunge deleted messages the size of your
folder will continue to increase until you are out of disk space.
<P>

<DT> <A NAME="expunge-wo-confirm"><EM>expunge-without-confirm</EM></A>

<DD> If set, you will not be prompted to confirm your intent before
the expunge takes place. Actually, you will still be prompted for confirmation
if the folder is not the <EM>INBOX</EM> folder or another folder in the
Incoming Folders collection. See the <EM>expunge-without-confirm-everywhere</EM>
feature which follows.
<P>
This feature is displayed as &quot;Expunge Without Confirming&quot;.
<P>

<DT> <A NAME="expunge-without-confirm-everywhere"><EM>expunge-without-confirm-everywhere</EM></A>

<DD> The regular <EM>expunge-without-confirm</EM> feature actually only
works for the <EM>INBOX</EM> folder and for other folders in the "Incoming
Folders" collection. If this feature is set then you also won't be prompted
to confirm expunges for all other folders.
<P>
This feature is displayed as &quot;Expunge Without Confirming Everywhere&quot;.
<P>

<DT> <A NAME="fcc-on-bounce"><EM>fcc-on-bounce</EM></A>

<DD> If set, normal Fcc (File Carbon Copy) processing will be
done for bounced messages,
just as if you had composed a message to the address you are
bouncing to. If not set, no Fcc of the message will be saved.
<P>
This feature is displayed as &quot;Include Fcc When Bouncing Messages&quot;.
<P>

<DT> <A NAME="fcc-only-without-confirm"><EM>fcc-only-without-confirm</EM></A>

<DD> This features controls an aspect of <EM>Alpine</EM>'s composer.
The only time this feature will be used is if you attempt to send mail
which has no recipients but does have an Fcc.
Normally, <EM>Alpine</EM> will ask if you really mean to copy the message only to
the Fcc.
That is, it asks if you really meant to have no recipients.
If this feature is set, you
will <B>not</B> be prompted to confirm your intent to make only a copy
of a message with no recipients.
<P>
This feature is closely related to
<A HREF="#warn-if-blank-to-and-cc-and-newsgroups"><EM>warn-if-blank-to-and-cc-and-newsgroups</EM></A>.
The difference between this feature and that feature is that this feature
considers a Bcc to be a recipient while that feature will ask for confirmation
even if there is a Bcc when there is no To, Cc, or Newsgroup.
The default values also differ. This feature defaults to asking the question
and you have to turn it off.
The warn-if-blank-to-and-cc-and-newsgroups feature defaults to not asking
unless you turn it on.
<P>
This feature is displayed as &quot;Send to Fcc Only Without Confirming&quot;.
<P>

<DT> <A NAME="fcc-without-attachments"><EM>fcc-without-attachments</EM></A>

<DD> This features controls the way FCC's (File Carbon Copies) are
made of the messages you send.

<P>
Normally, <EM>Alpine</EM> saves an exact copy of your message as it was sent.
When this feature is enabled, the &quot;body&quot; of the message
you send (the text you type in the composer) is preserved in the 
copy as before, however all attachments are replaced with text
explaining what had been sent rather than the attachments themselves.

<P>
This feature also affects <EM>Alpine</EM>'s &quot;Send ?&quot; confirmation prompt
in that a new &quot;^F Fcc Attchmnts&quot; option becomes available which
allows you to interactively set whether or not attachments are saved
to the Fcc'd copy.
<P>
This feature is displayed as &quot;Fcc Does Not Include Attachments&quot;.
<P>

<DT> <A NAME="force-arrow-cursor"><EM>force-arrow-cursor</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s MESSAGE INDEX display routine.
If set, the normal inverse-video cursor will be
replaced by a simple &quot;arrow&quot; cursor, which normally occupies the
second column of the index display.
<P>
This is the same index cursor you get if you turn on
<A HREF="#assume-slow-link">Assume-Slow-Link</A>, but the index
line coloring will still be present if this feature is turned on and
Assume-Slow-Link is off.
<P>
An alternative version of the Arrow cursor is available by including the
ARROW
token in the
<A HREF="#index-format"><EM>Index-Format</EM></A> option.
<P>
It ought to be the case that this feature also affects the ATTACHMENT INDEX,
but that is not implemented.
<P>

<DT> <A NAME="hide-nntp-path"><EM>hide-nntp-path</EM></A>

<DD> Normally the Path header that <EM>Alpine</EM> generates when posting to a newsgroup
contains the name of the computer from which the message is being sent and
the user name.
Some believe that this information is used by spammers.
If this feature is set, that information will be replaced with the text
<P>
<CENTER><SAMP>not-for-mail</SAMP></CENTER>
<P>
instead.
<P>
It should be noted that many servers being connected to will still reveal
the information that this feature attempts to protect.
<P>
<DT> <A NAME="include-attachments-in-reply"><EM>include-attachments-in-reply</EM></A>

<DD> If set, any MIME
attachments that were part of the original message will automatically be
included in a <EM>Reply</EM>.
<P>

<DT> <A NAME="include-header-in-reply"><EM>include-header-in-reply</EM></A>

<DD> If set, and a
message being replied to is included in the <EM>Reply</EM>,
then headers from that
message will also be part of the reply.
<P>

<DT> <A NAME="include-text-in-reply"><EM>include-text-in-reply</EM></A>

<DD> Normally, <EM>Alpine</EM> will ask whether you
wish to include the original message in your <EM>Reply</EM>.
If this feature is set and the feature
<A HREF="#enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A>
is <EM>not</EM> set, then the original message will be included in the reply
automatically, without prompting.
<P>

<DT> <A NAME="incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A>

<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
When incoming folder checking is turned on the default is to display
the number of unseen messages in each folder.
More precisely, it is the number of undeleted unseen messages.
Using this option you may also display the total number of messages
in each folder.
Instead of a single number representing the number of unseen messages
you will get two numbers separated by a slash character.
The first is the number of unseen messages and the second is the
total number of messages.
<P>
You may also use the recent message count instead of the unseen message
count by turning on the feature
<A HREF="#incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A>.
<P>

<DT> <A NAME="incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A>

<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
When incoming folder checking is turned on the default is to display
the number of unseen messages in each folder.
More precisely, it is the number of undeleted unseen messages.
Using this option you may display the number of recent messages instead
of the number of unseen messages.
A message is only counted as recent if this is the first session to
see it, so the recent count might be less than the unseen count.
The difference between the two would be accounted for by the unseen messages
in the folder which were there previously but have not been looked at yet.
<P>
If you simultaneously run more than one email client at a time
(for example, you run more than one <EM>Alpine</EM> in parallel) then turning
this feature on can cause some confusion.
The confusion stems from the fact that each message is only considered to be
recent in one session.
That means that the counts of new messages may be different in the two
<EM>Alpine</EM>s running side by side, because each incoming message will only be
counted as recent in one of the two sessions.
<P>
You may also display the total number of messages
in each folder by using the
<A HREF="#incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A>
option.
<P>

<DT> <A NAME="ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A>

<DD> This is only available if <EM>Alpine</EM> was linked with an LDAP library
when it was compiled.
If both the per-directory-server option
<A HREF="#use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A>
and this feature are set,
then when an implicit directory lookup is done from the
composer you will automatically be prompted to add the result of the
directory lookup to your address book.
<P>
This feature is displayed as &quot;LDAP Result to Addressbook Add&quot;.
<P>

<DT> <A NAME="maildrops-preserve-state"><EM>maildrops-preserve-state</EM></A>

<DD>
This feature affects the way
<A HREF="config-notes.html#maildrop">Mail Drops</A> work.
Normally, when mail is moved from a Mail Drop folder to a destination
folder, the state changes that have taken place since the mail was originally
delivered are lost.
Any Seen/New, Answered, Important/Flagged state that has changed will be
ignored.
All of the mail will be considered unSeen, unAnswered, and unImportant after
it is moved.
<P>
If this feature is set, then the state changes will not be lost.
<P>
In any case, messages which are already marked Deleted when the
mail is to be copied from the Mail Drop will be ignored.
<P>

<DT> <A NAME="mark-fcc-seen"><EM>mark-fcc-seen</EM></A>

<DD> This features controls the way FCCs (File Carbon Copies) are
made of the messages you send.
Normally, when <EM>Alpine</EM> saves a copy of a message you sent as an Fcc, that
copy will be marked as Unseen.
When you look at the folder it was saved in the message will appear to
be a New message until you read it.
When this feature is enabled, the message will be marked as having
been Seen.
<P>

<DT> <A NAME="mark-for-cc"><EM>mark-for-cc</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s MESSAGE INDEX display.
By default, a '+' is displayed in the first column if the
message is addressed directly to you.
When this feature is set and the message is not addressed to you, then a
'-' character is displayed if the message is instead Cc'd directly
to you.
<P>

<DT> <A NAME="mult-newsrc-hostnames-as-typed"><EM>mult-newsrc-hostnames-as-typed</EM></A>

<DD> This feature will be of little use to most users.
It has no effect unless the feature
<A HREF="#enable-multiple-newsrcs">Enable-Multiple-Newsrcs</A>
is set.

When the Enable-Multiple-Newsrcs feature is set
then the setting of this feature may have an effect on the names of the
newsrc files used.
Normally, the name of the news server will be canonicalized before it is
used in the newsrc file name.
For example, if you type the news server name

<P>
<CENTER><SAMP>servername</SAMP></CENTER>
<P>

it is likely that the canonical name will be something like

<P>
<CENTER><SAMP>servername.example.com</SAMP></CENTER>
<P>

Or it may be the case that

<P>
<CENTER><SAMP>servername.example.com</SAMP></CENTER>
<P>

is really an alias (a DNS CNAME) for

<P>
<CENTER><SAMP>othername.example.com</SAMP></CENTER>
<P>

If this feature is not set, then the canonicalized names will be used.
If this feature is set, then the name you typed in (or put in your
configuration) will be used.
<P>
This feature is displayed as &quot;Multiple Newsrc Hostnames as Typed&quot;.
<P>

<DT> <A NAME="news-approximates-new-status"><EM>news-approximates-new-status</EM></A>

<DD> This feature causes certain messages to be marked as <EM>New</EM> in the
MESSAGE INDEX of newsgroups.
This feature is set by default.
<P>

When opening a newsgroup, <EM>Alpine</EM> will consult
your <EM>newsrc</EM> file and
determine the last message you have previously disposed of via the <EM>D</EM>
key.  If this feature is set, any subsequent messages will be shown in the
Index with an <EM>N</EM>, and the first of these messages will be highlighted.
Although this is only an approximation of true <EM>New</EM> or <EM>Unseen</EM>
status, it provides a useful cue to distinguish more-or-less recent
messages from those you have seen previously, but are not yet ready to
mark deleted.
<P>

Background: your <EM>newsrc</EM> file (used to store message status information
for newsgroups) is only capable of storing a single flag, and <EM>Alpine</EM> uses
this to record whether or not you are "done with" a message, as
indicated by marking the message as <EM>Deleted</EM>.  Unfortunately, this
means that <EM>Alpine</EM> has no way to record exactly which messages you have
previously seen, so it normally does not show the <EM>N</EM> status flag for
any messages in a newsgroup. This feature enables a starting
<I>approximation</I> of seen/unseen status that may be useful.
<P>

<DT> <A NAME="news-deletes-across-groups"><EM>news-deletes-across-groups</EM></A>

<DD> This feature controls what <EM>Alpine</EM> does when you delete a
message in a newsgroup that appears in more than one newsgroup.
Such a message is sometimes termed a &quot;crossposting&quot;
in that it was posted across several newsgroups.

<P>
<EM>Alpine</EM>'s default behavior when you delete such a message is to remove
only the copy in the current newsgroup from view when you use the
&quot;Exclude&quot; command or the next time you visit the newsgroup.

<P>
Enabling this feature causes <EM>Alpine</EM> to remove every occurrence of the
message from all newsgroups it appears in and to which you are
subscribed.

<P>
NOTE: As currently implemented, enabling this feature may increase the
time it takes the Expunge command and newsgroup closing to complete.
<P>

<DT> <A NAME="news-offers-catchup-on-close"><EM>news-offers-catchup-on-close</EM></A>

<DD> This feature controls what <EM>Alpine</EM> does as it closes a newsgroup.
When set, <EM>Alpine</EM> will offer to delete all messages from the newsgroup
as you are quitting <EM>Alpine</EM> or opening a new folder.

<P>
This feature is useful if you typically read all the interesting messages
in a newsgroup each time you open it.  This feature saves you from
having to delete each message in a newsgroup as you read it or from
selecting all the messages and doing an
aggregate delete before you move on to the next folder or newsgroup.
<P>

<DT> <A NAME="news-post-without-validation"><EM>news-post-without-validation</EM></A>

<DD> This feature controls whether the NNTP server is queried as newsgroups
are entered for posting.  Validation over slow links (e.g. dialup using
SLIP or PPP) can cause delays.  Set this feature to eliminate such delays.
<P>

<DT> <A NAME="news-read-in-newsrc-order"><EM>news-read-in-newsrc-order</EM></A>

<DD> This feature controls the order that newsgroups will be presented.  If
set, they will be presented in the same order as they occur in
your <EM>newsrc</EM> file.
If not set, the newsgroups
will be presented in alphabetical order.
<P>

<DT> <A NAME="next-thread-without-confirm"><EM>next-thread-without-confirm</EM></A>

<DD> This feature controls an aspect of <EM>Alpine</EM>'s Next and Prev commands in
the case where you are using one of the
&quot;separate-index-screen&quot; styles for the configuration option
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A>
and currently have the folder sorted by a Threaded or OrderedSubject sort.
When you are Viewing a particular thread you have a
MESSAGE INDEX of only the messages in that thread.
If you press the Next command with the last message in the thread highlighted
you will normally be asked if you want to &quot;View next thread?&quot;,
assuming there is a next thread to view.
If this feature is set it will be assumed that you always want to view the
next thread and you won't be asked to confirm that.
Similarly, if the first message of the thread is highlighted and you
press the Prev command, this feature will prevent the question
&quot;View previous thread&quot;.
<P>
This feature only has an effect in the MESSAGE INDEX screen.
If you then view a particular message from that screen and press the
Next command, you will be sent to the next thread without being asked,
independent of the setting of this feature.
<P>
The feature
<A HREF="#auto-open-next-unread">auto-open-next-unread</A>,
also has some similar effects.
<P>
This feature is displayed as &quot;Read Next Thread Without Confirming&quot;.
<P>

<DT> <A NAME="offer-expunge-of-inbox"><EM>offer-expunge-of-inbox</EM></A>

<DD> The INBOX is normally treated differently from regular folders in several
ways.
One of the differences is that the normal &quot;close&quot; sequence of
events is deferred until <EM>Alpine</EM> is exited, instead of happening when you
leave the INBOX to view another folder.
The &quot;close&quot; sequence normally includes the Expunging
of deleted messages
(either automatically or after a prompt, controlled by the features
<A HREF="#expunge-wo-confirm">Expunge-Without-Confirm</A>,
<A HREF="#expunge-without-confirm-everywhere">Expunge-Without-Confirm-Everywhere</A>, and
<A HREF="#expunge-only-manually">Expunge-Only-Manually</A>), and the
handling of the
<A HREF="#read-msg-fold">Read-Message-Folder</A>.

<P>
If this feature is set the &quot;close&quot; sequence handling will take
place every time you leave the INBOX.
The INBOX will still be kept open, but the offer to Expunge and the archiving
to the Read-Message-Folder
will take place each time you leave the INBOX instead of only once at the
end of the session.
<P>

<DT> <A NAME="offer-expunge-of-stayopen-folders"><EM>offer-expunge-of-stayopen-folders</EM></A>

<DD> This feature is related to the option
<A HREF="#stay-open-folders">Stay-Open-Folders</A>.
Stay Open folders are treated differently from regular folders in several
ways.
One of the differences is that the normal &quot;close&quot; sequence of
events is deferred until <EM>Alpine</EM> is exited, instead of happening when you
leave the folder to view another folder.
The &quot;close&quot; sequence normally includes the Expunging
of deleted messages
(either automatically or after a prompt, controlled by the features
<A HREF="#expunge-wo-confirm">Expunge-Without-Confirm</A>,
<A HREF="#expunge-without-confirm-everywhere">Expunge-Without-Confirm-Everywhere</A>, and
<A HREF="#expunge-only-manually">Expunge-Only-Manually</A>), and the
handling of
<A HREF="#incoming-archive-folders">Incoming-Archive-Folders</A>.

<P>
If this feature is set the &quot;close&quot; sequence handling will take
place when you leave the Stay Open folder.
The folder will still be kept open, but the offer to Expunge and the archiving
will take place each time you leave the folder instead of only once at the
end of the session.
This feature does not affect the INBOX, which will still only be processed
when you exit <EM>Alpine</EM>.
<P>

<DT> <A NAME="pass-c1-control-characters-as-is"><EM>pass-c1-control-characters-as-is</EM></A>

<DD> It is probably not useful to set this option.
This is a legacy option left behind &quot;just in case&quot;.
Multi-byte characters which have an octet which has the same
value as a control character are permitted through whether or not
this option is turned on.
<P>
If the feature <A HREF="#pass-control-characters-as-is">pass-control-characters-as-is</A>
is set, then this feature has no effect.
However, if you wish to filter out regular control characters but pass the
so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
you may leave <A HREF="#pass-control-characters-as-is">pass-control-characters-as-is</A>
unset and set this feature.
<P>

<DT> <A NAME="pass-control-characters-as-is"><EM>pass-control-characters-as-is</EM></A>

<DD> It is probably not useful to set this option.
This is a legacy option left behind &quot;just in case&quot;.
Multi-byte characters which have an octet which has the same
value as a control character are permitted through whether or not
this option is turned on.
<P>
If set, all characters in a message will be sent to the
screen. Normally, control characters are automatically suppressed in
order to avoid inadvertently changing terminal setup parameters.
Control characters are usually displayed as two character sequences like
<P><CENTER><SAMP> ^C </SAMP></CENTER><P>
for Control-C,
<P><CENTER><SAMP> ^[ </SAMP></CENTER><P>
for ESCAPE,
<P><CENTER><SAMP> ^? </SAMP></CENTER><P>
for DELETE, and
<P><CENTER><SAMP> ~E </SAMP></CENTER><P>
for the character with value 133 (0x85).
(The DEL character is displayed as ^?, regular control characters are displayed
as the character ^ followed by the character obtained by adding the
five low-order bits of the character to 0x40, and the C1
control characters 0x80 - 0x9F are displayed as the character ~ followed by the
character obtained by adding the
five low-order bits of the character to 0x40.)
Sometimes, in cases where changing a single control character into a
two-character sequence would confuse <EM>Alpine</EM>'s display routines,
a question mark is substituted for the control character.
<P>
If you wish to filter out regular control characters but pass the
so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
you may leave this feature unset and set the feature <A HREF="#pass-c1-control-characters-as-is">pass-c1-control-characters-as-is</A> instead.
<P>

<DT> <A NAME="predict-nntp-server"><EM>predict-nntp-server</EM></A>

<DD> This feature allows <EM>Alpine</EM> to assume that the open NNTP server at the
time of composition is the NNTP server to which the message should be
posted.  This is especially recommended when there are multiple News
collections.  If this feature is not set, <EM>Alpine</EM> will try to post to the first server in
the <a href="#nntp-server">nntp-server</a> variable.  Setting
this feature also negates the need to add News collection servers to
the nntp-server variable.
<P>
This feature can be especially handy when used in conjunction with
<a href="#enable-multiple-newsrcs">enable-multiple-newsrcs</a>.
<P>
This option is displayed as &quot;NNTP Server (for news)&quot;.
<P>

<DT> <A NAME="prefer-plain-text"><EM>prefer-plain-text</EM></A>

<DD> A message being viewed may contain alternate versions of the same content.
Those alternate versions are ordered by the sending software such that the
first alternative is the least preferred and the last alternative is the
most preferred. <EM>Alpine</EM> will normally display the most-preferred version that
it knows how to display. This is most often encountered where the two
alternate versions are a plain text version and an HTML version, with the
HTML version listed last as the most preferred.
<P>

If this option is set, then any plain text version will be preferred to
all other versions.
<P>

<DT> <A NAME="preopen-stayopen-folders"><EM>preopen-stayopen-folders</EM></A>

<DD> This feature is related to the option
<A HREF="#stay-open-folders">Stay-Open-Folders</A>.
Normally, Stay Open folders are only opened on demand, when the user
asks to open them.
From then on they are kept open for the duration of the session.
However, if this feature is set, then the Stay Open folders will all be
opened at startup, at the same time that the INBOX is opened.
<P>

<DT> <A NAME="preserve-start-stop-characters"><EM>preserve-start-stop-characters</EM></A>

<DD> This feature controls how special control key characters, typically
<EM>^S</EM> and <EM>^Q</EM>, are interpreted when input to <EM>Alpine</EM>.
These characters
are known as the "start" and "stop" characters and are sometimes used in
communications paths to control data flow between devices that operate at
different speeds.
<P>

By default, <EM>Alpine</EM> turns the system's handling of these special characters
off except during printing.  However, if you see <EM>Alpine</EM> reporting input errors
such as:

<BLOCKQUOTE>
       [ Command "^Q" not defined for this screen. ] <BR>
</BLOCKQUOTE>

and, at the same time, see your display become garbled, then it is likely
that setting this option will solve the problem.  Be aware, though, that
enabling this feature will also cause <EM>Alpine</EM> to ostensibly "hang" 
whenever the <EM>Ctrl-S</EM> key combination is entered as the system is now
interpreting such input as a "stop output" command.  To "start
output"  again, simply type <EM>Ctrl-Q</EM>.
<P>
This feature is displayed as &quot;Preserve Start/Stop Characters&quot;.
<P>

<DT> <A NAME="print-formfeed-between-messages"><EM>print-formfeed-between-messages</EM></A>

<DD> Setting this feature causes a formfeed to be printed between messages when
printing multiple messages with the <EM>Apply Print</EM> command.
<P>

<DT> <A NAME="print-includes-from-line"><EM>print-includes-from-line</EM></A>

<DD> If this feature is set, then the Unix mail style From line is included
at the start of each message that is printed.  This line looks something
like the following, with the address replaced by the address from the
From line of the message being printed:
 
<BLOCKQUOTE>
    From user@domain.somewhere.com Mon May 13 14:11:06 1996 <BR>
</BLOCKQUOTE>
<P>

<DT> <A NAME="print-index-enabled"><EM>print-index-enabled</EM></A>

<DD> This feature controls the behavior of the <EM>Print</EM> command
when in the
"Folder Index" screen.
If set, the <EM>Print</EM> command will give you a prompt
asking if you wish to print the message index, or the currently highlighted
message. If not set, the message will be printed.
<P>

<DT> <A NAME="print-offers-custom-cmd-prompt"><EM>print-offers-custom-cmd-prompt</EM></A>

<DD> When this feature is set, the <EM>Print</EM> command
will have an additional
subcommand called <EM>C CustomPrint</EM>.
If selected, you will have
the opportunity to enter any system print command, instead of being 
restricted to using those that have been previously configured in the 
<EM>Setup/Printer</EM> screen.
<P>
This feature is displayed as &quot;Print Offers Custom Command Prompt&quot;.
<P>

<DT> <A NAME="prune-uses-yyyy-mm"><EM>prune-uses-yyyy-mm</EM></A>

<DD> By default, <EM>Alpine</EM> asks monthly whether or not you would like to rename
some folders to a new name containing the date.
It also asks whether or not you would like to delete some old folders.
See the <A HREF="#pruning-rule">pruning-rule</A> option for an
explanation.

<P>
By default, the name used when renaming a folder looks like
<P>
<CENTER><SAMP>&lt;foldername&gt;-&lt;month&gt;-&lt;year&gt;</SAMP></CENTER>
<P>
For example, the first time you run <EM>Alpine</EM> in May of 2004,
the folder &quot;sent-mail&quot; might be renamed to
<P>
<CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER>
<P>
If this feature is set, the name used will be of the form
<P>
<CENTER><SAMP>&lt;foldername&gt;-&lt;yyyy&gt;-&lt;mm&gt;</SAMP></CENTER>
<P>
where &quot;yyyy&quot; is the year and &quot;mm&quot; is the two-digit
month (01, 02, ..., 12).
For the April, 2004 example above, it would instead be
<P>
<CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER>
<P>
because April is the 4th month of the year.
A reason you might want to set this feature is so that the folders
will sort in chronological order.
<P>

<DT> <A NAME="publiccerts-in-keychain"><EM>publiccerts-in-keychain</EM></A>

<DD> Mac OS X <EM>Alpine</EM> only.
<P>
If this feature is set the Mac OS X default keychain will be used as the place
to store public certificates instead of a
<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>
or a
<A HREF="#smime-public-cert-container"><EM>smime-public-cert-container</EM></A>.
<P>
This feature is displayed as &quot;S/MIME -- Public Certs in MacOS Keychain&quot;.
<P>

<DT> <A NAME="quell-attachment-extension-warn"><EM>quell-attachment-extension-warn</EM></A>
<DD> This feature suppresses the extra warning you can get when trying
to view an attachment for which there is no mime-type match.  Turning
on this feature will just run the program according to extension
instead of first warning the user that it will run according to the
file's extension.
<P>
This feature can be used along side 
<A HREF="#quell-attachment-extra-prompt"><EM>quell-attachment-extra-prompt</EM></A>
to preserve the behavior exhibited in <EM>Pine</EM> versions prior to <EM>Pine</EM> 4.50.
<P>
This feature is displayed as &quot;Suppress Attachment Extension Warning&quot;.
<P>

<DT> <A NAME="quell-attachment-extra-prompt"><EM>quell-attachment-extra-prompt</EM></A>
<DD> By default, when you attempt to view an attachment externally
from the &quot;Attachment View&quot; screen, you are asked if you
really want to view the selected attachment.
<P>
If this feature is set, you will <B>not</B> be prompted to confirm
your selection.  Prior to <EM>Pine</EM> 4.50, the default behavior was to not
prompt. This feature was added for those wanting to preserve that
behavior.
<P>
This feature is displayed as &quot;Suppress Attachment Extra Prompt&quot;.
<P>

<DT> <A NAME="quell-berkeley-format-timezone"><EM>quell-berkeley-format-timezone</EM></A>

<DD> POSIX mandates a timezone in UNIX mailbox format folder delimiters
(the line which begins with From <SPACE>).
Some versions of Berkeley mail have trouble with this, and don't recognize
the line as a message delimiter.
If this feature is set, the timezone will be left off the delimiter line.
<P>
This feature is displayed as &quot;Suppress Berkeley Format Timezone&quot;.
<P>

<DT> <A NAME="quell-charset-warning"><EM>quell-charset-warning</EM></A>

<DD> By default, if the message you are viewing contains characters that are
not representable in your
<A HREF="#disp-char-set"><EM>display-character-set</EM></A>
then <EM>Alpine</EM> will
add a warning to the start of the displayed text.
If this option is set, then that editorial message will be suppressed.
<P>
Setting this feature also suppresses the comment about the character set
in header lines.
For example, when viewing a message you might see
<P>
<CENTER><SAMP>From: &quot;[ISO-8859-2] Name&quot; &lt;address&gt;</SAMP></CENTER>
<P>
in the From header if your Character-Set is something other than ISO-8859-2.
If you set this feature, the comment about the character set will
no longer be there.
<P>
This feature is displayed as &quot;Suppress Character Set Warning&quot;.
<P>

<DT> <A NAME="quell-content-id"><EM>quell-content-id</EM></A>

<DD> This feature changes the behavior of <EM>Alpine</EM> when sending messages.
It is intended to work around a bug in Microsoft's Outlook XP mail user
agent.
As of this writing, Microsoft has acknowledged the bug but
has not added it to the Knowledge Base.
We have been told that there will be a post-SP1 hotfix for Outlook XP.
This particular bug has bug fix number OfficeQFE:4781.
The nature of the bug is that messages with attachments which
contain a Content-ID header (which standard <EM>Alpine</EM> attachments do)
do not show the attachment indicator (a paperclip) when viewed with
Outlook XP.
So the user has no indication that the message contains an attachment.

<P>
If this feature is set then <EM>Alpine</EM> will remove most Content-ID headers
before sending a message.
If an attachment is of type MESSAGE, then the existing Content-ID headers
inside the message will be left intact.
This would only happen with <EM>Alpine</EM> if a message was forwarded as an attachment
or if a message with a message attached was forwarded.
Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded,
the Content-ID headers of the alternative parts will not be removed.

<P>
Because the Content-ID header is a standard part of MIME it is possible
that setting this feature will break something.
For example, if an attachment has a Content-ID header which is necessary
for the correct functioning of that attachment, it is possible that <EM>Alpine</EM>
may remove that header when the attachment is forwarded.
However, it seems fairly safe at this time.
<P>
This feature is displayed as &quot;Suppress Content-ID&quot;.
<P>

<DT> <A NAME="quell-dead-letter-on-cancel"><EM>quell-dead-letter-on-cancel</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when you cancel a message being
composed.  <EM>Alpine</EM>'s usual behavior is to write the canceled message to
a file named <CODE>dead.letter</CODE> in your home directory (under UNIX;
<CODE>DEADLETR</CODE> under WINDOWS/DOS) overwriting any previous message.
Under some conditions (some routine), this can introduce a noticeable delay.
<P>
 
Setting this feature will cause <EM>Alpine</EM> NOT to write canceled compositions
into the file called <CODE>dead.letter</CODE>.
<P>
This feature affects the newer option
<A HREF="#dead-letter-files"><EM>Dead-Letter-Files</EM></A>, which specifies the
number of dead letter files to keep around.
If this feature is set, then the Dead-Letter-Files option has no effect.
<P>
This feature is displayed as &quot;Do Not Save to Deadletter on Cancel&quot;.
<P>

<DT> <A NAME="quell-empty-directories"><EM>quell-empty-directories</EM></A>

<DD> This feature causes <EM>Alpine</EM> to remove from the display any directories
that do not contain at least one file or directory.  This can be useful
to prevent overly cluttered folder lists when a collection is stored on
a server that treats all names as both a folder and a directory.

<P>
Note, enabling this feature can cause surprising behavior!  For example,
you can still use Add to create a directory, but unless you immediately
enter that directory and create a folder, that newly created directory
may not be displayed next time you enter the folder list.

<P>
This feature is displayed as &quot;Hide Empty Directories&quot;.
<P>

<DT> <A NAME="quell-extra-post-prompt"><EM>quell-extra-post-prompt</EM></A>

<DD> This feature causes <EM>Alpine</EM> to skip the extra question about
posting a message which may go to thousands of readers when you
are about to post to a newsgroup.

<P>
This feature is displayed as &quot;Suppress Extra Posting Prompt&quot;.
<P>

<DT> <A NAME="quell-filtering-done-message"><EM>quell-filtering-done-message</EM></A>

<DD> This feature causes <EM>Alpine</EM> to suppress the &quot;filtering done&quot; message.

<P>
This feature is displayed as &quot;Suppress Filtering Done Message&quot;.
<P>

<DT> <A NAME="quell-filtering-messages"><EM>quell-filtering-messages</EM></A>

<DD> This feature causes <EM>Alpine</EM> to suppress the messages about
moving filtered messages and setting flags in messages, due to Filter Rules.

<P>
This feature is displayed as &quot;Suppress Filtering Messages&quot;.
<P>

<DT> <A NAME="quell-flowed-text"><EM>quell-flowed-text</EM></A>

<DD> <EM>Alpine</EM> generates flowed text where possible.
The method for generating flowed text is defined by
<A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>,
the benefit of doing so is
to send message text that can properly be viewed both on normal width displays
and on displays with smaller or larger than normal screen widths.
With flowed text, a space at the end of a line tells the receiving mail
client that the following line belongs to the same paragraph.
Quoted text will also be affected, with only the innermost
level of &quot;&gt;&quot; quoting being followed by a space.
However, if you have changed the
<A HREF="#reply-ind-str">&quot;Reply-Indent-String&quot;</A>
so that it is not equal to the default value of &quot;&gt;&nbsp;&quot;, then
quoted text will not be flowed.
For this reason, we recommend that you leave your
&quot;Reply-Indent-String&quot; set to the default.
<P>
This feature turns off the generation of flowed text, as it might be
desired to more tightly control how a message is displayed on the receiving end.
<P>
If this feature is <EM>not</EM> set, you can control on a message by message
basis whether or not flowed text is generated.
You do this by typing ^V at the Send confirmation prompt that you get
after typing ^X to send a message.
^V is a toggle which turns flowing off and back on if typed again.
If for some reason flowing cannot be done on a particular message, then the
^V command will not be available.
This would be the case, for example, if this feature was set, or if your
&quot;Reply-Indent-String&quot; was set to a non-default value.
If the feature
<A HREF="#send-without-confirm">Send-Without-Confirm</A> is set,
then the opportunity to control on a message by message basis
whether or not flowed text is generated is lost.
<P>
When this feature is not set and you have typed ^V to turn off flowing,
the Send confirmation prompt will change to look like
<P>
<CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER>
<P>
<A HREF="#strip-whitespace-before-send">Strip-Whitespace-Before-Send</A> will
also turn off the sending of flowed text messages, but it differs in that
it also trims all trailing white space from a message before sending it.
<P>
If alternate editors are used extensively, be aware that a message will still
be sent flowed if this feature is unset.  In most cases this will be fine,
but if the editor has a &quot;flowed text&quot; mode, it would be best to
use that.
<P>
This feature is displayed as &quot;Do Not Send Flowed Text&quot;.
<P>

<DT> <A NAME="quell-folder-internal-msg"><EM>quell-folder-internal-msg</EM></A>

<DD> This feature determines whether or not <EM>Alpine</EM> will create 
&quot;pseudo messages&quot; in folders that are in standard Unix or 
MMDF format.
<P> 

<EM>Alpine</EM> will normally create these
pseudo messages when they are not already
present in a standard Unix or MMDF folder.
Their purpose is to record
certain mailbox state data needed for correct IMAP and POP server operation,
and also for <EM>Alpine</EM> to be able to mark messages as Answered when
the Reply has been postponed.
<P>

Sites which do not use IMAP/POP for remote mail access, and which need to
support mail tools that are adversely affected by the presence of the
pseudo-messages (e.g. some mail notification tools) may enable this
feature to tell <EM>Alpine</EM> not to create them.
Note that <EM>Alpine</EM>'s &quot;Answered&quot; flag
capability will be adversely affected if this is done.
<P>

Note too that, even if this feature is enabled, <EM>Alpine</EM> will not remove
pseudo-messages when it encounters them (e.g. those created by UW's imapd
or ipopd servers.)
This feature has no effect on folders that are not in
standard Unix or MMDF format, as pseudo-messages are not needed in the
other formats to record mailbox state information.
<P>
This feature is displayed as &quot;Prevent Folder Internal Message&quot;.
<P>

<DT> <A NAME="quell-full-header-auto-reset"><EM>quell-full-header-auto-reset</EM></A>

<DD> The HdrMode Command
normally resets to the default state when switching to a new message.
For example, if you've used the &quot;H&quot; command to turn on Full
Headers for a message you are viewing, and then you type the Next command
to look at the next message, the full headers will no longer be shown.
Setting this feature disables that reset.
Instead, the Header Mode remains the same from message to message.

<P>
The presence or absence of the HdrMode command is determined by the
<A HREF="#enable-full-header-cmd">&quot;Enable-Full-Header-Cmd&quot;</A>
Feature-List option.
<P>
This feature is displayed as &quot;Suppress Full Header Auto Reset&quot;.
<P>

<DT> <A NAME="quell-imap-envelope-update"><EM>quell-imap-envelope-update</EM></A>

<DD> In the MESSAGE INDEX screen, if the open folder is being accessed
using IMAP, <EM>Alpine</EM> normally tries to paint the index lines on the screen
as soon as the information arrives from the IMAP server.
This means that the index information makes it onto the screen more quickly
than it otherwise would.
This sometimes results in behavior that bothers some users.
For example, when paging to a new page of the index, it may be possible for
the lines to be painted on the screen in a random order, rather than from
top to bottom.
<P>

Setting this feature causes <EM>Alpine</EM> to wait for all of the information
to be gathered before it paints the index screen.
Once it collects all of the information, the screen will be painted quickly
from top to bottom.
<P>
This feature is displayed as &quot;Suppress IMAP Envelope Update&quot;.
<P>

<DT> <A NAME="quell-lock-failure-warnings"><EM>quell-lock-failure-warnings</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when it encounters a problem
acquiring a mail folder lock.  Typically, a secondary file associated
with the mail folder being opened is created as part of the locking
process.  On some systems, such file creation has been administratively
precluded by the system configuration.
<P>

<EM>Alpine</EM> issues a warning when such failures occur, which can become bothersome
if the system is configured to disallow such actions.  Setting this
feature causes <EM>Alpine</EM> to remain silent when this part of lock creation fails.
<P>

WARNING: systems that have been configured in a way that precludes locking
introduce some risk of mail folder corruption when more than one program
attempts to modify the mail folder.  This is most likely to occur to one's
<EM>INBOX</EM> or other "Incoming Message Folder".
<P>
This feature is displayed as &quot;Suppress Lock Failure Warnings&quot;.
<P>

<DT> <A NAME="quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A>

<DD> This option is closely related to the
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A>
option, the
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A> option, and
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A>.
<P>
If this option is set, then the normal new-mail checking which happens
while you are composing will not happen for folders other than your
INBOX (which depends on the setting
of &quot;Quell-Mailchecks-Composing-Inbox&quot;).
<P>
You might want to set this option if you are experiencing delays while
composing which you think might be related to the speed of the new-mail
checks.
<P>
Even with this option turned on, an occasional new-mail check may be done
in order to keep the server from killing the connection to the folder.
For example, IMAP servers may remove a connection to a folder if there
has been no activity on the connection for 30 minutes or more.
Instead of letting that happen, <EM>Alpine</EM> will check for new mail before the
30 minutes is up even though you have turned on this feature to quell
those checks.
<P>
Besides new-mail checks, checkpoint operations on the folders
will also be quelled when you set this option.
The purpose of checkpointing is to write the changes to a folder out to
disk periodically in order to avoid losing those changes when system or
software problems occur.
New-mail checking and checkpointing while you are not composing are not
affected by this option.
<P>
This feature is displayed as &quot;Prevent Mailchecks While Composing Except for INBOX&quot;.
<P>

<DT> <A NAME="quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A>

<DD> This option is closely related to the
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A>
option, the
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A> option, and
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A>.
<P>
If this option is set, then the normal new-mail checking which happens
while you are composing will not happen for your INBOX.
Checking of other folders is controlled in a similar way with the
&quot;Quell-Mailchecks-Composing-Except-Inbox&quot; option.
<P>
You might want to set this option if you are experiencing delays while
composing which you think might be related to the speed of the new-mail
checks.
<P>
Even with this option turned on, an occasional new-mail check may be done
in order to keep the server from killing the connection to the folder.
For example, IMAP servers may remove a connection to a folder if there
has been no activity on the connection for 30 minutes or more.
Instead of letting that happen, <EM>Alpine</EM> will check for new mail before the
30 minutes is up even though you have turned on this feature to quell
those checks.
<P>
Besides new-mail checks, checkpoint operations on the INBOX
will also be quelled when you set this option.
The purpose of checkpointing is to write the changes to a folder out to
disk periodically in order to avoid losing those changes when system or
software problems occur.
New-mail checking and checkpointing while you are not composing are not
affected by this option.
<P>
This feature is displayed as &quot;Prevent Mailchecks While Composing for INBOX&quot;.
<P>

<DT> <A NAME="quell-maildomain-warning"><EM>quell-maildomain-warning</EM></A>

<DD> When your configuration is set up so that your domain name contains no dots,
it is usually a configuration error.
By default, <EM>Alpine</EM> will warn you about this when you start it up.
You will see a warning message that looks like
<P>
<CENTER><SAMP>Incomplete maildomain &quot;&lt;domain&gt;&quot;.</SAMP></CENTER>

<P>
If this feature is set, the warning is turned off.
This feature is displayed as &quot;Suppress Maildomain Warning&quot;.
<P>

<DT> <A NAME="quell-news-envelope-update"><EM>quell-news-envelope-update</EM></A>

<DD> In the MESSAGE INDEX screen, if the open folder is being accessed
using NNTP (News), <EM>Alpine</EM> normally tries to paint the index lines on the screen
as soon as the information arrives from the NNTP server.
This means that the index information makes it onto the screen more quickly
than it otherwise would.
This sometimes results in behavior that bothers some users.
For example, when paging to a new page of the index, it may be possible for
the lines to be painted on the screen in a random order, rather than from
top to bottom.
<P>

Setting this feature causes <EM>Alpine</EM> to wait for all of the information
to be gathered before it paints the index screen.
Once it collects all of the information, the screen will be painted quickly
from top to bottom.
<P>
This feature is displayed as &quot;Suppress News Envelope Update&quot;.
<P>

<DT> <A NAME="quell-partial-fetching"><EM>quell-partial-fetching</EM></A>

<DD> Partial fetching is a feature of the IMAP protocol.
By default, <EM>Alpine</EM>
will use partial fetching when copying the contents of a message or attachment
from the IMAP server to <EM>Alpine</EM>.
This means that the fetch will be done in many
small chunks instead of one big chunk. The main benefit of this approach is
that the fetch becomes interruptible. That is, the user can type <EM>^C</EM>
to stop the fetch early. In some cases partial fetching may cause a performance
problem so that the fetching of data takes significantly longer when partial
fetching is used. Turning on this feature will turn off partial fetching.
<P>
This feature is displayed as &quot;Prevent Partial Fetching&quot;.
<P>

<DT> <A NAME="quell-personal-name-prompt"><EM>quell-personal-name-prompt</EM></A>

<DD> <EM>PC-Alpine</EM> only.  This feature quells the prompting for a 
<A HREF="#personal-name">personal-name</A>.  This prompt normally happens
before composing a message, and only happens when there is no personal name
already set.
<P>

<DT> <A NAME="quell-server-after-link-in-html"><EM>quell-server-after-link-in-html</EM></A>

<DD> By default, links in HTML text are displayed with the host the link
references appended, within square brackets, to the link text.  <EM>Alpine</EM>
does this to help indicate where a link will take you, particularly when
the link text might suggest a different destination.

<P>
Setting this feature will prevent the server name from being appended
to the displayed text.
<P>
This feature is displayed as &quot;Suppress Server After Link in HTML&quot;.
<P>

<DT> <A NAME="quell-ssl-largeblocks"><EM>quell-ssl-largeblocks</EM></A>

<DD> This feature (<EM>PC-Alpine</EM> only) changes the behavior of fetching messages
and attachments so that the message data is fetched in chunks no larger
than 12K bytes.
This works around a bug in Microsoft's SSL/TLS support.
Some versions of Microsoft SSL are not able to read full-sized (16K)
SSL/TLS packets.
Some servers will send such packets and this will
cause <EM>PC-Alpine</EM> to crash with the error

<P>
<CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER>

<P>
Microsoft is aware of the problem and has developed a hotfix for it, but as of
this writing the hotfix has not yet been added to the Knowledge Base.
<P>
This feature is displayed as &quot;Prevent SSL Largeblocks&quot;.
<P>

<DT> <A NAME="quell-status-message-beeping"><EM>quell-status-message-beeping</EM></A>

<DD> If set status messages will never emit a beep.
<P>
This feature is displayed as &quot;Suppress Status Message Beeping&quot;.
<P>

<DT> <A NAME="quell-timezone-comment-when-sending"><EM>quell-timezone-comment-when-sending</EM></A>

<DD> Normally, when <EM>Alpine</EM> generates a Date header for outgoing mail,
it will try to include the symbolic timezone at the end of the
header inside parentheses.
The symbolic timezone is often three characters long, but on
some operating systems, it may be longer.
Apparently there are some SMTP servers in the world which will reject an
incoming message if it has a Date header longer than about 80 characters.
If this feature is set, the symbolic timezone normally generated by
<EM>Alpine</EM> will not be included.
You probably don't need to worry about this feature unless you run into
the problem described above.
<P>
This feature is displayed as &quot;Suppress Timezone Comment When Sending&quot;.
<P>

<DT> <A NAME="quell-user-id-prompt"><EM>quell-user-id-prompt</EM></A>

<DD> <EM>PC-Alpine</EM> only.  This feature quells the prompting for a
<A HREF="#user-id">user-id</A>
if the information can be obtained from the login name used
to open the INBOX.  Normally, this prompt happens before composing
a message, and only happens when there is no user-id already set
in the configuration.
<P>
With this feature set, composing a message is only possible after
establishing a connection to the INBOX.
<P>

<DT> <A NAME="quell-user-lookup-in-passwd-file"><EM>quell-user-lookup-in-passwd-file</EM></A>

<DD> This feature controls an aspect of
<EM>Alpine</EM>'s Composer, and if needed, will usually be set by the
system manager in <EM>Alpine</EM>'s system-wide configuration file.
Specifically, if this feature is set, <EM>Alpine</EM> will not attempt to look
in the system password file to find a Full Name for the entered address.
<P>

Normally, names you enter into address fields (e.g. To: or Cc:) are
checked against your address book(s) to see if they match an address book
nickname.
Failing that, (in Unix <EM>Alpine</EM>) the name is then checked against
the Unix password file.  If the entered name matches a username in the
system password file, <EM>Alpine</EM> extracts the corresponding Full Name information
for that individual, and adds that to the address being entered.
<P>

However, password file matching can have surprising (incorrect) results if
other users of the system do not receive mail at the domain you are using.
That is, if either the <A HREF="#user-domain"><EM>user-domain</EM></A>
or <A HREF="#use-only"><EM>use-only-domain-name</EM></A> option
is set such that the administrative domain of other users on the system
isn't accurately reflected, <EM>Alpine</EM> should be told that a password
file match is coincidental,
and Full Name info will be incorrect.
For example, a
personal name from the password file could get falsely paired with the
entered name as it is turned into an address in the configured domain.
<P>

If you are seeing this behavior, enabling this feature will prevent Unix
<EM>Alpine</EM> from looking up names in the password file to find the Full Name
for incomplete addresses you enter.
<P>
This feature is displayed as &quot;Prevent User Lookup in Password File&quot;.
<P>

<DT> <A NAME="quit-without-confirm"><EM>quit-without-confirm</EM></A>

<DD> This feature controls whether or not <EM>Alpine</EM> will ask for confirmation when a
<EM>Quit</EM> command is received.
<P>
This feature is displayed as &quot;Quit Without Confirming&quot;.
<P>

<DT> <A NAME="quote-replace-nonflowed"><EM>quote-replace-nonflowed</EM></A>

<DD> This feature, which is only active when
<A HREF="#quote-replace-string">Quote-Replace-String</A> is
also set,
enables quote-replacement on non-flowed messages.  It is off
by default because a non-flowed message is more dependent on its format,
and thus quote-replacement may cause less-than-pleasing results.
Setting this feature will cause quote-replacement similar to that of flowed
messages, but with the added possibility of long lines being wrapped
into new lines if the Quote-Replacement-String is longer than the string
it is replacing, which is &quot;&gt;&nbsp;&quot;.

<P>

<DT> <A NAME="reply-always-uses-reply-to"><EM>reply-always-uses-reply-to</EM></A>

<DD> If set, <EM>Alpine</EM>
will not prompt when a message being replied to contains a <EM>Reply-To:</EM>
header value, but will simply use its value (as opposed to using the
<EM>From:</EM> field's value).
<P>

<DT> <A NAME="return-to-inbox-without-confirm"><EM>return-to-inbox-without-confirm</EM></A>

<DD>
Normally, when you use the TAB
command and there are no more folders or newsgroups to visit, you are asked
if you want to return to the INBOX.
If this feature is set you will not be asked.
It will be assumed that you do want to return to the INBOX.
<P>
This feature is displayed as &quot;Return to INBOX Without Confirming&quot;.
<P>

<DT> <A NAME="save-aggregates-copy-sequence"><EM>save-aggregates-copy-sequence</EM></A>

<DD> This feature will optimize an aggregate copy operation, if
possible, by issuing a single IMAP <EM>COPY</EM> command with a
list of the messages to be copied.
This feature is set by default.
This may reduce network traffic and elapsed time for the Save.
<EM>However, many IMAP servers (including the UW IMAP server) do
not preserve the order of messages when this optimization is applied.</EM>
If this feature is not set,
<EM>Alpine</EM> will copy each message individually and the order of the
messages will be preserved.
<P>
This feature is displayed as &quot;Save Combines Copies (may be out of order)&quot;.
<P>

<DT> <A NAME="save-partial-wo-confirm"><EM>save-partial-msg-without-confirm</EM></A>

<DD> This feature controls an aspect of <EM>Alpine</EM>'s Save command.
By default, when you Save a message that has some deleted parts, you will
be asked to confirm that you want to Save with a prompt that looks like:
<P>
<CENTER><SAMP>Saved copy will NOT include entire message!  Continue?</SAMP></CENTER>
<P>
If this feature is set, you will not be asked.
<P>
This feature is displayed as &quot;Save Partial Message Without Confirming&quot;.
<P>

<DT> <A NAME="save-will-advance"><EM>save-will-advance</EM></A>

<DD> If set, <EM>Save</EM> will
(in addition to copying the current message to the designated folder) also
advance to the next message.
<P>

<DT> <A NAME="save-will-not-delete"><EM>save-will-not-delete</EM></A>

<DD> If set, <EM>Save</EM> will
not mark the message Deleted (its default behavior) after it has been
copied to the designated folder.
<P>

<DT> <A NAME="save-will-quote"><EM>save-will-quote-leading-froms</EM></A>

<DD> This feature controls an aspect of the <EM>Save</EM> command
(and also the way
outgoing messages are saved to an FCC folder).  If set, <EM>Alpine</EM> will add
a leading <CODE>&gt;</CODE> character in front of message
lines beginning with "From" when they are
saved to another folder, including lines syntactically
distinguishable from the type of message separator line commonly used on
Unix systems.
<P>
 
The default behavior is that a <CODE>&gt;</CODE> will be prepended only to lines
beginning with "From " that might otherwise be confused with a message
separator line on Unix systems.  If <EM>Alpine</EM> is the only mail program you use,
this default is reasonable.  If another program you use has trouble
displaying a message with an unquoted From saved by <EM>Alpine</EM>, you should
enable this feature.  This feature only applies to the common Unix mailbox
format that uses message separator lines beginning with "From ".  If
<EM>Alpine</EM> has been configured to use a different mailbox format (possibly
incompatible with other mail programs), then this issue does not arise,
and the feature is irrelevant.
<P>

<DT> <A NAME="scramble-message-id"><EM>scramble-message-id</EM></A>

<DD> Normally the Message-ID header that <EM>Alpine</EM> generates when sending a message
contains the name of the computer from which the message is being sent.
Some believe that this hostname could be used by spammers or could
be used by others for nefarious purposes.
If this feature is set, that name will be transformed with a simple
Rot13 transformation.
The result will still have the correct syntax for a Message-ID but the
part of the MessageID that is often a domain name will not be an actual
domain name because the letters will be scrambled.
<P>
It is possible (but unlikely?) that some spam detection
software will use that as a reason to reject the mail as spam.
It has also been reported that some spam detection software uses the
fact that there are no dots after the &quot;@&quot; as a reason to reject
messages.
If your <EM>PC-Alpine</EM> Message-ID is using a name without a dot that is because
that is what Windows thinks is your &quot;Full computer name&quot;.
The method used to set this varies from one type of Windows to another but
check under Settings -> Control Panel -> System and
look for Network Identification or Computer Name or something similar.
How to set it is beyond the scope of <EM>Alpine</EM>.
<P>
This feature is displayed as &quot;Scramble the Message-ID When Sending&quot;.
<P>

<DT> <A NAME="select-without-confirm"><EM>select-without-confirm</EM></A>

<DD> This feature controls an aspect of
<EM>Alpine</EM>'s <EM>Save</EM>, <EM>Export</EM>, and <EM>Goto</EM> commands.
These commands all take text input to specify the name of the folder or
file to be used, but allow you to press <EM>^T</EM> for a
list of possible names.
If set, the selected name will be used immediately, without further
opportunity to confirm or edit the name.
<P>
This feature is displayed as &quot;Select Ctrl-T Foldername Without Confirming&quot;.
<P>

<DT> <A NAME="send-without-confirm"><EM>send-without-confirm</EM></A>

<DD> By default, when you send or post a message you will be asked to confirm
with a question that looks something like:

<P>
<CENTER><SAMP>Send message?</SAMP></CENTER>
<P>

If this feature is set, you
will <B>not</B> be prompted to confirm your intent to send
and your message will be sent.
<P>
If this feature is set it disables some possibilities and renders some
other features meaningless.
You will not be able to use
<A HREF="#sending-filters">Sending Filters</A>,
Verbose sending mode,
<A HREF="#enable-background-sending">Background Sending</A>,
<A HREF="#enable-delivery-status-notification">Delivery Status Notifications</A>,
or ^V to turn off the generation of flowed text for this message.
These options are normally available as suboptions in the Send prompt, but
with no Send prompt the options are gone.

<P>
A somewhat related feature is
<A HREF="#quell-extra-post-prompt">quell-extra-post-prompt</A>.
which may be used to eliminate the extra confirmation
question when posting to a newsgroup.
<P>
This feature is displayed as &quot;Send Without Confirming&quot;.
<P>

<DT> <A NAME="separate-folder-and-directory-display"><EM>separate-folder-and-directory-display</EM></A>

<DD> This feature affects folder collections wherein a folder
and directory can have the same name.  By default, <EM>Alpine</EM> displays them
only once, denoting that it is both a folder and directory by appending
the folder name with the hierarchy character enclosed
in square brackets.
<P>

Enabling this feature will cause <EM>Alpine</EM> to display such names
separately marking the name representing a directory with a trailing
hierarchy delimiter (typically the slash, &quot;/&quot;, character).
<P>

The feature also alters the command set slightly.  By default, the
right-arrow descends into the directory, while hitting the Return key will
cause the folder by that name to be opened.
<P>

With this feature set, the Return key will open the highlighted folder, or
enter the highlighted directory.
<P>

<DT> <A NAME="show-cursor"><EM>show-cursor</EM></A>

<DD> If set, the system
cursor will move to convenient locations in the displays.  For example,
to the beginning of the status field of the highlighted index line, or
to the highlighted word after a successful <EM>WhereIs</EM> command.
It is intended to draw your attention to the <EM>interesting</EM>
spot on the screen.
<P>

<DT> <A NAME="show-plain-text-internally"><EM>show-plain-text-internally</EM></A>

<DD> This feature modifies the method <EM>Alpine</EM> uses to display Text/Plain
MIME attachments from the Attachment Index screen.  Normally, the
&quot;View&quot; command searches for any externally defined (usually
via the Mailcap file) viewer,
and displays the selected text within that viewer.

<P>
Enabling this feature causes <EM>Alpine</EM> to ignore any external viewer
settings and always display text with <EM>Alpine</EM>'s internal viewer.

<P>

<DT> <A NAME="show-selected-in-boldface"><EM>show-selected-in-boldface</EM></A>

<DD> This feature controls an aspect of <EM>Alpine</EM>'s aggregate operation commands;
in particular, the <EM>Select</EM> and <EM>WhereIs</EM> commands.
<EM>Select</EM> and <EM>WhereIs</EM> (with
the <EM>^X</EM> subcommand) will search the current folder
for messages meeting a
specified criteria, and <EM>tag</EM> the resulting
messages with an <EM>X</EM> in the
first column of the applicable lines in the "Folder Index". If this feature
is set, instead of using the <EM>X</EM> to denote a selected message,
<EM>Alpine</EM> will attempt to display those index lines in boldface.
Whether this is preferable to the <EM>X</EM> will depend on personal
taste and the type of terminal being used.
<P>

<DT> <A NAME="show-sort"><EM>show-sort</EM></A>

<DD> If this feature is set and there is sufficient space on the screen,
a short indication of the current sort order will be
added in the titlebar (the top line on the screen), before the name
of the folder.
For example, with the default Arrival sort in effect,
the display would have the characters

<P><CENTER>[A]</CENTER><P>

added between the title of the screen and the folder name.
The letters are the same as the letters you may type to manually
sort a folder with the SortIndex command ($).
The letters in the table below are the ones that may show
up in the titlebar line.
<P>
<TABLE>   
<TR> <TD> A </TD> <TD> <EM>A</EM>rrival        </TD> </TR>
<TR> <TD> S </TD> <TD> <EM>S</EM>ubject        </TD> </TR>
<TR> <TD> F </TD> <TD> <EM>F</EM>rom          </TD> </TR>
<TR> <TD> T </TD> <TD> <EM>T</EM>o             </TD> </TR>
<TR> <TD> C </TD> <TD> <EM>C</EM>c             </TD> </TR>
<TR> <TD> D </TD> <TD> <EM>D</EM>ate           </TD> </TR>
<TR> <TD> Z </TD> <TD> si<EM>Z</EM>e           </TD> </TR>
<TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR>
<TR> <TD> E </TD> <TD> scor<EM>E</EM>          </TD> </TR>
<TR> <TD> H </TD> <TD> t<EM>H</EM>read         </TD> </TR>
</TABLE>
<P>
If the sort order is Reversed, the letter above will be preceded by the letter
&quot;R&quot;, for example

<P><CENTER>[RS]</CENTER><P>

means that a Reverse Subject sort is in effect.
For the case where the sort is in Reverse Arrival order, the &quot;A&quot; is
left out, and just an &quot;R&quot; is shown.

<P><CENTER>[R]</CENTER>
<P>
This feature is displayed as &quot;Show Sort in Titlebar&quot;.
<P>

<DT> <A NAME="sig-at-bot"><EM>signature-at-bottom</EM></A>

<DD> If this feature
is set, and a message being <EM>Repl</EM>ied to is being included in
the reply, then the
contents of the signature file (if any) will be inserted after the included
message.
This feature does not affect the results of a <EM>Forward</EM> command.
<P>

<DT> <A NAME="single-column-folder-list"><EM>single-column-folder-list</EM></A>

<DD> If set, the "Folder List" screen will list one folder per line
instead of several per line.
<P>

<DT> <A NAME="slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A>

<DD> Normally, the Collapse/Expand Thread command Collapses or Expands the subthread which
starts at the currently highlighted message, if any.
If this feature is set, then the slash command Collapses or Expands the
<EM>entire</EM> current thread instead of just the subthread.
<P>

<DT> <A NAME="smime-dont-do-smime"><EM>smime-dont-do-smime</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
Setting this feature turns off all of <EM>Alpine</EM>'s S/MIME support.
You might want to set this if you are having trouble due to the S/MIME support.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This feature is displayed as &quot;S/MIME -- Turn off S/MIME&quot;.
<P>

<DT> <A NAME="smime-encrypt-by-default"><EM>smime-encrypt-by-default</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature only has an effect if your version of <EM>Alpine</EM> includes
support for S/MIME.
It affects <EM>Alpine</EM>'s behavior when you send a message.
If this option is set, the &quot;Encrypt&quot; option will default to ON when sending messages.
<P>
Only the default value is affected.
In any case, you may still toggle the Encrypt option on or off before sending
with the &quot;E Encrypt&quot; command (provided you have a the public digital ID
for the recipient).
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This feature is displayed as &quot;S/MIME -- Encrypt by Default&quot;.
<P>

<DT> <A NAME="smime-remember-passphrase"><EM>smime-remember-passphrase</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature only has an effect if your version of <EM>Alpine</EM> includes
support for S/MIME.
If this option is set, you will only have to enter your passphrase for your private key
once during an <EM>Alpine</EM> session.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This feature is displayed as &quot;S/MIME -- Remember S/MIME Passphrase&quot;.
<P>

<DT> <A NAME="smime-sign-by-default"><EM>smime-sign-by-default</EM></A>

<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature only has an effect if your version of <EM>Alpine</EM> includes
support for S/MIME.
It affects <EM>Alpine</EM>'s behavior when you send a message.
If this option is set, the &quot;Sign&quot; option will default to ON when sending messages.
<P>
Only the default value is affected.
In any case, you may still toggle the Signing option on or off before sending
with the &quot;G Sign&quot; command (provided you have a personal digital ID
certificate).
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This feature is displayed as &quot;S/MIME -- Sign by Default&quot;.
<P>

<DT> <A NAME="sort-default-fcc-alpha"><EM>sort-default-fcc-alpha</EM></A>

<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen.
If set, the default FCC folder will be sorted alphabetically with the other
folders instead of appearing right after the INBOX.
<P>
This feature is displayed as &quot;Sort Default Fcc Folder Alphabetically&quot;.
<P>

<DT> <A NAME="sort-default-save-alpha"><EM>sort-default-save-alpha</EM></A>

<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen.
If set, the default save folder will be sorted alphabetically with the other
folders instead of appearing right after the INBOX (and default FCC folder).
<P>
This feature is displayed as &quot;Sort Default Save Folder Alphabetically&quot;.
<P>

<DT> <A NAME="spell-check-before-sending"><EM>spell-check-before-sending</EM></A>

<DD> When this feature is set, every composed message will be spell-checked before
being sent.

<P>

<DT> <A NAME="store-window-position-in-config"><EM>store-window-position-in-config</EM></A>

<DD> Normally, <EM>PC-Alpine</EM> will store its window size and position in the
Windows Registry.
This is convenient if you want to use the same remote
configuration from more than one PC.
If you use multiple configuration files to start <EM>PC-Alpine</EM>, you may want
to store the window size and position in the configuration file instead
of in the Registry.
Setting this feature causes that to happen.

<P>

<DT> <A NAME="strip-from-sigdashes-on-reply"><EM>strip-from-sigdashes-on-reply</EM></A>

<DD> This feature doesn't do anything if the feature
<A HREF="#enable-sigdashes"><EM>enable-sigdashes</EM></A> is turned on.
However, if the <EM>enable-sigdashes</EM> feature is not turned on,
then turning on this feature enables support for the convention
of not including text beyond the sigdashes line when Replying or Following
up to a message and including the text of that message.
<P>
In other words, this is a way to turn on the signature stripping behavior
without also turning on the dashes-adding behavior.
<P>

<DT> <A NAME="strip-whitespace-before-send"><EM>strip-whitespace-before=send</EM></A>

<DD> Trailing whitespace is not stripped from
a message before sending.  Trailing whitespace should have no effect on an
email message, and in flowed text can aid in delimiting paragraphs.
However, the old behavior of stripping trailing whitespace was in place
to better deal with older clients that couldn't handle certain types of
text encodings.  This feature restores the old behavior
<P>
Trailing whitespace is of aid to flowed-text-formatted messages, which are
generated by default but can be turned off via the
<A HREF="#quell-flowed-text">quell-flowed-text</A> feature.
strip-whitespace-before-send also has the effect of turning off sending
of flowed text.
<P>
This feature is displayed as &quot;Strip Whitespace Before Sending&quot;.
<P>

<DT> <A NAME="suppress-asterisks-in-password-prompt"><EM>suppress-asterisks-in-password-prompt</EM></A>

<DD> When you are running <EM>Alpine</EM> you will sometimes be asked for a password
in a prompt on the third line from the bottom of the screen.
Normally each password character you type will cause an asterisk to echo
on the screen. That gives you some feedback to know that your typing is
being recognized.
There is a very slight security risk in doing it this way because someone
watching over your shoulder might be able to see how many characters there
are in your password.
If you'd like to suppress the echoing of the asterisks set this feature.
<P>

<DT> <A NAME="suppress-user-agent-when-sending"><EM>suppress-user-agent-when-sending</EM></A>
<DD> If this feature is set then <EM>Alpine</EM> will not generate a
<CODE>User-Agent</CODE> header in outgoing messages.
<P>

<DT> <A NAME="tab-checks-recent"><EM>tab-checks-recent</EM></A>

<DD> In a FOLDER LIST screen, the TAB key usually just changes which
folder is highlighted.
If this feature is set, then the TAB key will cause the number of
recent messages and the total number of messages in the highlighted folder
to be displayed instead.
<P>
This feature is displayed as &quot;Tab Checks for Recent Messages&quot;.
<P>

<DT> <A NAME="tab-uses-unseen-for-next-folder"><EM>tab-uses-unseen-for-next-folder</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when using the TAB
NextNew Command
to move from one folder to the next.
<EM>Alpine</EM>'s usual behavior is to search for folders
with <EM>Recent</EM> messages in them.
Recent messages are messages which have arrived since the last time the
folder was opened.

<P>
Setting this feature causes <EM>Alpine</EM> to search for <EM>Unseen</EM>
messages instead of Recent messages.
Unseen messages remain Unseen until you view them (or flag then as Seen with
the Flag Command).
Setting this feature allows you to locate messages you have not read
instead of only recently received messages.
When this feature is set, the feature
<A HREF="#enable-fast-recent-test">Enable-Fast-Recent-Test</A>
will have no effect, so the checking may be slower.

<P>
Another reason why you might want to use this feature is that <EM>Alpine</EM> sometimes
opens folders implicitly behind the scenes, and this clears the
Recent status of all messages in the folder.
One example where this happens is when Saving or filtering a
message to another folder.
If that message has some <A HREF="#keywords">keywords</A>
set, then because of some shortcomings
in the IMAP specification, the best way to ensure that those keywords are
still set in the saved copy of the message is to open the folder and
set the keywords explicitly.
Because this clears the Recent status of all messages in that folder the
folder will not be found by the NextNew command unless this feature is set.
<P>

<DT> <A NAME="tab-visits-next-new-message-only"><EM>tab-visits-next-new-message-only</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when using the <EM>TAB</EM>
key to move from one message to the next.
<EM>Alpine</EM>'s usual behavior is to select the next
<EM>Unread</EM> message or message flagged as <EM>Important</EM>.
<P>
 
Setting this feature causes <EM>Alpine</EM> to skip the
messages flagged as <EM>Important</EM>,
and select <EM>Unread</EM> messages exclusively.
Tab behavior when there are no
new messages left to select remains unchanged.
<P>

<DT> <A NAME="termdef-takes-precedence"><EM>termdef-takes-precedence</EM></A>

<DD> This feature may affect <EM>Alpine</EM>'s low-level input routines.  Termcap (or
terminfo, depending on how your copy of <EM>Alpine</EM> was compiled and linked)
is the name of the database which describes terminal capabilities.  In
particular, it describes the sequences of characters that various keys
will emit.

<P>
An example would be the Up Arrow key on the keyboard.  Up
Arrow is not a distinct character on most Unix systems.  When you press
the Up Arrow key a short sequence of characters are produced.  This
sequence is supposed to be described in the termcap database by the
&quot;ku&quot; capability (or by the &quot;kcuu1&quot; capability if you
are using terminfo instead of termcap).

<P>
By default, <EM>Alpine</EM> defines some terminal
escape sequences that are commonly used.  For example, the sequence
&quot;ESC&nbsp;O&nbsp;A&quot; is recognized as an Up Arrow key.  The sequence
&quot;ESC&nbsp;[&nbsp;A&quot;
is also recognized as an Up Arrow key.  These are chosen because common
terminals like VT100's or ANSI standard terminals produce these
sequences when you press the Up Arrow key.

<P>
If your system's termcap
(terminfo) database assigns some other function to the sequence
&quot;ESC&nbsp;O&nbsp;A&quot;
it is usually ignored by <EM>Alpine</EM>.  Also, if your termcap (terminfo)
database assigns a sequence which doesn't begin with an escape
character (<SAMP>ESC</SAMP>) it is usually ignored by <EM>Alpine</EM>.
This usually works fine
because most terminals emit the escape sequences that <EM>Alpine</EM> has defined
by default.  We have also found that it is usually better to have these
defaults take precedence over the definitions contained in the database
because the defaults are more likely to be correct than the database.

<P>
There are some terminals where this breaks down.  If you want <EM>Alpine</EM> to
believe the definitions given in your termcap (terminfo) database in
preference to the defaults the <EM>Alpine</EM> itself sets up, then you may turn
this feature on.  Then, sequences of characters which are defined in
both termcap (terminfo) and in <EM>Alpine</EM>'s set of defaults will be
interpreted the way that termcap (terminfo) says they should be
interpreted.  Also, if your terminal capabilities database assigns a
sequence which doesn't begin with escape, it will not be ignored.
<P>

<DT> <A NAME="thread-index-shows-important-color"><EM>thread-index-shows-important-color</EM></A>

<DD> This option affects only the THREAD INDEX screen.
Whether or not you ever see a THREAD INDEX screen depends on the setting
of the configuration option
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A>
and on the sort order of the index.
If a message within a thread is flagged as Important
and this option is set, then
the entire line in the THREAD INDEX will be colored the color of the
Index-important Symbol, which can be set using the
Setup Kolor screen.
<P>

<DT> <A NAME="try-alternative-authentication-driver-first"><EM>try-alternative-authentication-driver-first</EM></A>

<DD> This feature affects how <EM>Alpine</EM> connects to IMAP servers.
It's utility has largely been overtaken by events,
but it may still be useful in some circumstances.
If you only connect to modern IMAP servers that support
&quot;TLS&quot; you can ignore this feature.

<P>
Details:

<P>
By default, <EM>Alpine</EM> will attempt to connect to an IMAP server on the
normal IMAP service port (143), and if the server offers &quot;Transport Layer
Security&quot; (TLS) and <EM>Alpine</EM> has been compiled with encryption capability,
then a secure (encrypted) session will be negotiated.

<P>
With this feature enabled, before connecting on the normal IMAP port, <EM>Alpine</EM>
will first attempt to connect to an alternate IMAP service port (993) used
specifically for encrypted IMAP sessions via the Secure Sockets Layer
(SSL) method.
If the SSL attempt fails, <EM>Alpine</EM> will then try the default
behavior described in the previous paragraph.

<P>
TLS negotiation on the normal port is preferred, and supersedes the use of
SSL on port 993, but older servers may not provide TLS support.
This feature may be convenient when accessing IMAP servers that do not support
TLS, but do support SSL connections on port 993.
However, it is important to understand that with this feature enabled,
<EM>Alpine</EM> will <EM>attempt</EM> to make a secure connection if that is possible,
but it will proceed to make an insecure connection if that is the only
option offered by the server, or if the <EM>Alpine</EM> in question has been built
without encryption capability.

<P>
Note that this feature specifies a per-user (or system-wide) default
behavior, but host/folder specification flags may be used to control the
behavior of any specific connection.
This feature interacts with some of
the possible host/folder path specification flags as follows:

<P>
The <SAMP>/tls</SAMP> host flag, for example,

<P>
<CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER>
<P>
will over-ride this feature for the specified host by bypassing the
SSL connection attempt.
Moreover, with <SAMP>/tls</SAMP> specified,
the connection attempt will fail if the
service on port 143 does not offer TLS support.

<P>
The <SAMP>/ssl</SAMP> host flag, for example,

<P>
<CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
<P>
will insist on an SSL connection for the specified host,
and will fail if the SSL service on port 993 is not available.
<EM>Alpine</EM> will not subsequently retry a connection
on port 143 if <SAMP>/ssl</SAMP> is specified.
<P>

<DT> <A NAME="unselect-will-not-advance"><EM>unselect-will-not-advance</EM></A>

<DD> Normally, when the Unselect current message command (:) is typed when the
current message is selected, the message will be unselected and the next
message will become the current message.
If this feature is set, the cursor will not advance to the next message.
Instead, the current message will remain the current message after
unselecting.
<P>

<DT> <A NAME="use-current-dir"><EM>use-current-dir</EM></A>

<DD> This feature controls an aspect of several commands. If set, your
"current working directory" will be used instead of your home directory
for all of the following operations:

<UL>
<LI> <EM>Export</EM> in the "Folder Index" and "Message Text" screens
<LI> Attachment <EM>Save</EM> in the "Message Text" and "Attachment Text" screens
<LI> <EM>^R</EM> file inclusion in the Composer
<LI> <EM>^J</EM> file attachment in the Composer
</UL>
<P>
This feature is displayed as &quot;Use Current Directory&quot;.
<P>

<DT> <A NAME="use-function-keys"><EM>use-function-keys</EM></A>

<DD> This feature specifies that <EM>Alpine</EM> will
respond to function keys instead of
the normal single-letter commands. In this mode, the key menus at the
bottom of each screen will show function key designations instead of the
normal mnemonic key.
<P>

<DT> <A NAME="use-reg-start-rule"><EM>use-regular-startup-rule-for-stayopen-folders</EM></A>

<DD> This feature affects which message is selected as the current message
when you enter a
<A HREF="#stay-open-folders">Stay Open</A> folder.
<P>
Normally, the starting position for an incoming folder (which most Stay Open
folders will likely be) is controlled by the
<A HREF="#incoming-startup-rule"><EM>Incoming-Startup-Rule</EM></A>.
However, if a folder is a Stay Open folder, when you re-enter the folder
after the first time the current message will be the same as it was when
you left the folder.
An exception is made if you use the TAB command to get to the folder.
In that case, the message number will be incremented by one from what it
was when you left the folder.
<P>
The above special behavior is thought to be useful.
However, it is special and different from what you might at first expect.
If this feature is set, then Stay Open folders will not be treated specially
as far as the startup rule is concerned.
<P>

<DT> <A NAME="use-resent-to-in-rules"><EM>use-resent-to-in-rules</EM></A>

<DD> This feature is turned off by default because turning it on causes problems
with some deficient IMAP servers.
In <EM>Alpine</EM> Filters and other types of Rules, if the
Pattern
contains a To header pattern and this feature is turned on,
then a check is made in the message to see
if a Resent-To header is present, and that is used instead of the To header.
If this feature is not turned on, then the regular To header will always
be used.
<P>

<DT> <A NAME="use-sender-not-x-sender"><EM>use-sender-not-x-sender</EM></A>

<DD> Normally <EM>Alpine</EM> on Unix adds a header line labeled <EM>X-X-Sender</EM>,
if the sender is different from the <EM>From:</EM> line.

<P>
The standard specifies that this header
line should be labeled <EM>Sender</EM>, not <EM>X-X-Sender</EM>.
Setting this feature causes
<EM>Sender</EM> to be used instead of <EM>X-X-Sender</EM>.  The standard also states
that the data associated with this header field should not be used as a Reply address.
Unfortunately, certain implementations of mail list management servers will use the
Sender address for such purposes.  These implementations often even recognize the
<EM>X-Sender</EM> fields as being equivalent to the <EM>Sender</EM> field, and use it
if present.  This is why <EM>Alpine</EM> defaults to <EM>X-X-Sender</EM>.
<P>
Note, <EM>PC-Alpine</EM> always adds
either an <EM>X-X-Sender</EM> line if there is an open, remote mailbox, or an
<EM>X-Warning: UNAuthenticated User</EM> otherwise

<P>
This feature is displayed as &quot;Use Sender Instead of X-X-Sender&quot;.
<P>

<DT> <A NAME="use-subshell-for-suspend"><EM>use-subshell-for-suspend</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when process suspension
is enabled and then activated via the <EM>^Z</EM> key.
<EM>Alpine</EM> suspension allows one to
temporarily interact with the operating system command "shell" without
quitting <EM>Alpine</EM>,
and then subsequently resume the still-active <EM>Alpine</EM> session.
<P>

When the <EM>enable-suspend</EM> feature is set and subsequently the
<EM>^Z</EM> key is pressed,
<EM>Alpine</EM> will normally suspend itself and return temporary
control to <EM>Alpine</EM>'s parent shell process.
However, if this feature is set, <EM>Alpine</EM> will instead create an
inferior subshell process.
This is useful when the parent process is not intended to be used
interactively.
Examples include invoking <EM>Alpine</EM> via the <CODE>-e</CODE> argument
of the Unix <EM>xterm</EM> program, or via a menu system.
<P>

Note that one typically resumes a suspended <EM>Alpine</EM> by entering the Unix
<EM>fg</EM> command, but if this feature is set, it will be necessary to enter
the <EM>exit</EM> command instead.
<P>

<DT> <A NAME="use-system-translation"><EM>use-system-translation</EM></A>

<DD> UNIX <EM>Alpine</EM> only. <EM>Alpine</EM> normally uses its own internal software to convert between the multi-byte
representation of characters and the Unicode representation of those
same characters
( see the section on <A HREF="low-level.html#char-set">International Character Sets</EM></A>).
It converts from the multi-byte characters your keyboard produces to Unicode,
and from Unicode to the multi-byte characters your display expects.
Alpine also uses its own internal software to decide how much space on
the screen a particular Unicode character will occupy.

<P>
Setting this feature tells <EM>Alpine</EM> to use the system-supplied routines to
perform these tasks instead.
In particular there are three tasks and three system routines that will
be used for these tasks.

<P>
To convert from multi-byte to Unicode the routine

<P>
<CENTER><SAMP>mbstowcs</SAMP></CENTER>
<P>

is used.
To convert from Unicode to multi-byte the routine

<P>
<CENTER><SAMP>wcrtomb</SAMP></CENTER>
<P>

is used.
And to find the screen width a particular Unicode character will
occupy the routine used is

<P>
<CENTER><SAMP>wcwidth</SAMP></CENTER>
<P>

This feature has been only lightly tested.
The internal routines should normally be used unless you run into
a problem that you think may be solved by using the system routines.
Note that your environment needs to be set up for these
routines to work correctly.
In particular, the LANG or LC_CTYPE variable in your environment will
need to be set.
<P>

<DT> <A NAME="vertical-folder-list"><EM>vertical-folder-list</EM></A>

<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen.  If set,
the folders will be listed alphabetically down the columns rather
than across the columns as is the default.

<P>
This feature is displayed as &quot;Use Vertical Folder List&quot;.
<P>

<DT> <A NAME="warn-if-blank-subject"><EM>warn-if-blank-subject</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when you send a message being
composed.
If this option is set, <EM>Alpine</EM> will check to see if the message about to be sent
has a subject or not.
If not, you will be asked if you want to send the message anyway.
<P>

<DT> <A NAME="warn-if-blank-to-and-cc-and-newsgroups"><EM>warn-if-blank-to-and-cc-and-newsgroups</EM></A>

<DD> This feature affects <EM>Alpine</EM>'s behavior when you send a message being
composed.
If this option is set, <EM>Alpine</EM> will check to see if the message about to be sent
has either a To address, a Cc address, or a Newsgroup.
If none of these is set,
you will be asked if you want to send the message anyway.
<P>
This feature is closely related to
<A HREF="#fcc-only-without-confirm"><EM>fcc-only-without-confirm</EM></A>.
<EM>Alpine</EM> will normally ask if you want to copy a message only to the Fcc.
This feature also applies to cases where there is a Bcc but still no To, Cc,
or Newsgroup.
If the Fcc-Only-Without-Confirm feature is set and you are sending a
message with only an Fcc, then you won't be asked about sending with
a blank To and Cc and Newsgroups header even if this feature is set.
Similarly, if you have already been asked if you want to send to the Fcc
only and you have answered Yes, then you won't be asked again about sending with
blank To, Cc, and Newsgroups headers even if this feature is set.

<P>

</DL>
<P>

<H2><A NAME="hidden-config">Hidden Config Variables and Features</A></H2>

There are several configuration variables and features which are normally hidden
from the user. That is, they don't appear on any of the configuration
screens. Some of these are suppressed because they are intended to be used
by system administrators, and in fact may only be set in system-wide
configuration files. Others are available to users but are thought to be
of such little value to most users that their presence on the Config
screens would cause more confusion than help.
Others are hidden in the Setup/Config screen because they are normally
configured in one of the other configuration screens. For example, all
of the colors are hidden because the normal way to configure colors is 
through Setup/Colors not Setup/Config.
You may set the feature <A HREF="#expose-hidden-config">expose-hidden-config</A>
to cause most of these hidden variables and features to show up at the bottom
of the Setup/Config screen.

<H3>Hidden Variables Not Settable by Users</H3>

These variables are settable only in system-wide configuration files.

<UL>
<LI> <A HREF="#bugs-add">bugs-additional-data</A>
<LI> <A HREF="#bugs">bugs-address</A>
<LI> <A HREF="#bugs">bugs-fullname</A>
<LI> <A HREF="#forced-abook">forced-abook-entry</A>
<LI> <A HREF="#kblock-count">kblock-passwd-count</A>
<LI> <A HREF="#bugs">local-address</A>
<LI> <A HREF="#bugs">local-fullname</A>
<LI> <A HREF="#mail-directory">mail-directory</A>
<LI> <A HREF="#standard-printer">standard-printer</A>
<LI> <A HREF="#bugs">suggest-address</A>
<LI> <A HREF="#bugs">suggest-fullname</A>
</UL>

<H3>Hidden Variables Which are Settable by Users</H3>

These variables are not shown to users but are settable by means
of hand editing the personal configuration file. This first group
is usually maintained by <EM>Alpine</EM> and there will usually
be no reason to edit them by hand.

<UL>
<LI> <A HREF="#last-version-used">last-version-used</A>
<LI> <A HREF="#patterns-filters2">patterns-filters2</A>
<LI> <A HREF="#patterns-indexcolors">patterns-indexcolors</A>
<LI> <A HREF="#patterns-roles">patterns-roles</A>
<LI> <A HREF="#patterns-scores2">patterns-scores2</A>
<LI> <A HREF="#remote-abook-metafile">remote-abook-metafile</A>
</UL>
<P>

This group is usually correct but may be changed by system managers or
users in special cases.

<UL>
<LI> <A HREF="#disable-these-auths">disable-these-authenticators</A>
<LI> <A HREF="#disable-these-drivers">disable-these-drivers</A>
<LI> <A HREF="#last-time">last-time-prune-questioned</A>
<LI> <A HREF="#new-version-threshold">new-version-threshold</A>
<LI> <A HREF="#remote-abook-history">remote-abook-history</A>
<LI> <A HREF="#remote-abook-validity">remote-abook-validity</A>
<LI> <A HREF="#rsh-command">rsh-command</A>
<LI> <A HREF="#rsh-open-timeout">rsh-open-timeout</A>
<LI> <A HREF="#rsh-path">rsh-path</A>
<LI> <A HREF="#sendmail-path">sendmail-path</A>
<LI> <A HREF="#ssh-command">ssh-command</A>
<LI> <A HREF="#ssh-open-timeout">ssh-open-timeout</A>
<LI> <A HREF="#ssh-path">ssh-path</A>
<LI> <A HREF="#tcp-open-timeout">tcp-open-timeout</A>
<LI> <A HREF="#tcp-query-timeout">tcp-query-timeout</A>
<LI> <A HREF="#tcp-read-warning-timeout">tcp-read-warning-timeout</A>
<LI> <A HREF="#tcp-write-warning-timeout">tcp-write-warning-timeout</A>
<LI> <A HREF="#use-function-keys">use-function-keys</A>
</UL>
<P>

System managers are usually interested in setting these in the system-wide
configuration files, though users may set them if they wish.

<UL>
<LI> <A HREF="#operating-dir">operating-dir</A>
<LI> <A HREF="#user-input">user-input-timeout</A>
</UL>
<P>

<H3>Hidden Features Which are Settable by Users</H3>

These are <EM>features</EM> (as opposed to variables) which users or system
administrators may set. Some of them only make sense for administrators.
To turn these on manually, the configuration file should be edited and the
feature added to the <EM>feature-list</EM> variable.
You may set the feature <A HREF="#expose-hidden-config">expose-hidden-config</A>
to cause these hidden features to show up in the Setup/Config screen.
They will be at the bottom of the screen.

<UL>
<LI> <A HREF="#disable-config-cmd">disable-config-cmd</A>
<LI> <A HREF="#disable-kblock">disable-keyboard-lock-cmd</A>
<LI> <A HREF="#disable-password-cmd">disable-password-cmd</A>
<LI> <A HREF="#disable-pipes-in-sigs">disable-pipes-in-sigs</A>
<LI> <A HREF="#disable-pipes-in-templates">disable-pipes-in-templates</A>
<LI> <A HREF="#disable-roles-setup-cmd">disable-roles-setup-cmd</A>
<LI> <A HREF="#disable-roles-sig-edit">disable-roles-sig-edit</A>
<LI> <A HREF="#disable-roles-template-edit">disable-roles-template-edit</A>
<LI> <A HREF="#disable-setlocale-collate">disable-setlocale-collate</A>
<LI> <A HREF="#disable-shared-namespaces">disable-shared-namespaces</A>
<LI> <A HREF="#disable-signature-edit-cmd">disable-signature-edit-cmd</A>
</UL>
<P>

<H2><A NAME="ret-var">Retired Variables and Features</A></H2>

Variables and features that are no longer used by the current <EM>Alpine</EM> version.
When an obsolete variable is encountered, its value is applied to any new
corresponding setting.
The replaced values include:
<P>

<DL COMPACT>

<DT> <EM>character-set</EM>

<DD> Replaced by three separate variables:
<EM>display-character-set</EM>,
<EM>keyboard-character-set</EM>, and
<EM>posting-character-set</EM>.

<DT> <EM>compose-mime</EM>

<DT> <EM>elm-style-save</EM>

<DD> Replaced by <EM>saved-msg-name-rule</EM>

<DT> <EM>feature-level</EM>

<DD> Replaced by <EM>feature-list.</EM>

<DT> <EM>header-in-reply</EM>

<DD> Replaced by <EM>include-header-in-reply</EM> in the
<EM>feature-list.</EM>

<DT> <EM>old-style-reply</EM>

<DD> Replaced by <EM>signature-at-bottom</EM> in the
<EM>feature-list.</EM>

<DT> <EM>use-old-unix-format-write</EM>

<DD> No replacement.

<DT> <EM>patterns</EM>

<DD> Replaced by four separate patterns variables:
<EM>patterns-roles</EM>,
<EM>patterns-filters</EM>,
<EM>patterns-scores</EM>, and
<EM>patterns-indexcolors</EM>.
Since then, <EM>patterns-filters</EM> has also become obsolete and is replaced
by <EM>patterns-filters2</EM>; <EM>patterns-scores</EM> is replaced by
<EM>patterns-scores2</EM>.

<DT> <EM>save-by-sender</EM>

<DD> Replaced by <EM>saved-msg-name-rule.</EM>

<DT> <EM>show-all-characters</EM>

<DD> No replacement, it always works this way now.

</DL>

<P>

<H2><A NAME="index-tokens"></A>Tokens for Index and Replying</H2>

This set of special tokens may be used in the
<A HREF="#index-format"><EM>index-format</EM></A> option,
in the <A HREF="#reply-leadin"><EM>reply-leadin</EM></A> option,
in signature files,
in template files used in
<A HREF="#role-config"><EM>roles</EM></A>,
and in the folder name that is the target of a Filter Rule.
Some of them aren't available in all situations.
<P>
The tokens are used as they appear below for the <EM>Index-Format</EM>
option, but they must be surrounded by underscores for the
<EM>Reply-Leadin</EM> option, in signature and template files,
and in the target of Filter Rules.
<P>

<H3><EM>Tokens Available for all Cases (except Filter Rules)</EM></H3>

<DL>
<DT>SUBJECT</DT>
<DD>
This token represents the Subject the sender gave the message.
Alternatives for use in the index screen are
SUBJKEY, SUBJKEYINIT, SUBJECTTEXT, SUBJKEYTEXT, and SUBJKEYINITTEXT.
You may color the subject text in the MESSAGE INDEX screen differently by using the
<A HREF="#index-subject-color">Index Subject Color</A>
and the
<A HREF="#index-opening-color">Index Opening Color</A>.
options available from
the Setup Kolor screen.
</DD>

<DT>FROM</DT>
<DD>
This token represents the personal name (or email address if the name
is unavailable) of the person specified in the message's &quot;From:&quot;
header field.
You may color the from text in the MESSAGE INDEX screen differently by using the
<A HREF="#index-from-color">Index From Color</A>
option available from the Setup Kolor screen.
</DD>

<DT>ADDRESS</DT>
<DD>
This is similar to the &quot;FROM&quot; token, only it is always the
email address, never the personal name.
For example, &quot;mailbox@domain&quot;.
</DD>

<DT>MAILBOX</DT>
<DD>
This is the same as the &quot;ADDRESS&quot; except that the 
domain part of the address is left off.
For example, &quot;mailbox&quot;.
</DD>

<DT>SENDER</DT>
<DD>
This token represents the personal name (or email address) of the person
listed in the message's &quot;Sender:&quot; header field.
</DD>

<DT>TO</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's &quot;To:&quot; header field.
</DD>

<DT>NEWSANDTO</DT>
<DD>
This token represents the newsgroups from the
message's &quot;Newsgroups:&quot; header field <EM>and</EM>
the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's &quot;To:&quot; header field.
</DD>

<DT>TOANDNEWS</DT>
<DD>
Same as &quot;NEWSANDTO&quot; except in the opposite order.
</DD>

<DT>NEWS</DT>
<DD>
This token represents the newsgroups from the
message's &quot;Newsgroups:&quot; header field.
</DD>

<DT>CC</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's &quot;Cc:&quot; header field.
</DD>

<DT>RECIPS</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in both the
message's &quot;To:&quot; header field and
the message's &quot;Cc:&quot; header field.
</DD>

<DT>NEWSANDRECIPS</DT>
<DD>
This token represents the newsgroups from the
message's &quot;Newsgroups:&quot; header field <EM>and</EM>
the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's &quot;To:&quot; and &quot;Cc:&quot; header fields.
</DD>

<DT>RECIPSANDNEWS</DT>
<DD>
Same as &quot;NEWSANDRECIPS&quot; except in the opposite order.
</DD>

<DT>INIT</DT>
<DD>
This token represents the initials from the personal name
of the person specified in the message's &quot;From:&quot;
header field.
If there is no personal name, it is blank.
</DD>

<DT>DATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format MMM DD. For example, &quot;Oct 23&quot;.
The feature
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>,
which adjusts for the timezone the message was sent from,
may have an affect on the value of this token as well as the values of
all of the other DATE or TIME tokens.
Some of the DATE and TIME tokens are displayed in a locale-specific
way unless the option
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is set.
</DD>

<DT>SMARTDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It is &quot;Today&quot; if the message was sent today,
&quot;Yesterday&quot; for yesterday,
&quot;Wednesday&quot; if it was last Wednesday, and so on. If the
message is from last year and is more than six months old it includes the year, as well.
There is no adjustment made for different time zones, so you'll get
the day the message was sent according to the time zone the sender
was in.
See the SMARTDATE alternatives below, as well.
</DD>

<DT>SMARTTIME</DT>
<DD>
This token represents the most relevant elements of the date on which
the message was sent (according to the &quot;Date&quot; header field),
in a compact form. If the message was sent today, only the time is used
(e.g. &quot;9:22am&quot;, &quot;10:07pm&quot;); if it was sent during
the past week, the day of the week and the hour are used
(e.g. &quot;Wed09am&quot;, &quot;Thu10pm&quot;); other dates are
given as date, month, and year (e.g. &quot;23Aug00&quot;,
&quot;9Apr98&quot;).
There is no adjustment made for different time zones, so you'll get
the day/time the message was sent according to the time zone the sender
was in.
</DD>

<DT>SMARTDATETIME</DT>
<DD>
This is a combination of SMARTDATE and SMARTTIME.
It is SMARTDATE unless the SMARTDATE value is &quot;Today&quot;, in which
case it is SMARTTIME.
See the SMARTDATETIME alternatives below, as well.
</DD>

<DT>DATEISO</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format YYYY-MM-DD. For example, &quot;1998-10-23&quot;.
</DD>

<DT>SHORTDATEISO</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format YY-MM-DD. For example, &quot;98-10-23&quot;.
</DD>

<DT>SHORTDATE1</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format MM/DD/YY. For example, &quot;10/23/98&quot;.
</DD>

<DT>SHORTDATE2</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format DD/MM/YY. For example, &quot;23/10/98&quot;.
</DD>

<DT>SHORTDATE3</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format DD.MM.YY. For example, &quot;23.10.98&quot;.
</DD>

<DT>SHORTDATE4</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format YY.MM.DD. For example, &quot;98.10.23&quot;.
</DD>

<DT>LONGDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It has the format MMM DD, YYYY. For example, &quot;Oct 23, 1998&quot;.
</DD>

<DT>SMARTDATE alternatives</DT>
<DD>
There are several versions of SMARTDATE which are all the same except
for the way they format dates far in the past.
SMARTDATE formats the date using the information from your locale settings
to format the date string. It may end up formatting dates so that they look
like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
The feature
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>
may have an affect on the values of these tokens.
If you want more control you may use one of the following.
  <DL>
  <DT>SMARTDATE</DT> <DD>If the option
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is not set
then this will be locale specific. Control this with the
LC_TIME locale setting on a UNIX system. On Windows
the Regional Options control panel may be used to set the Short date
format. At the programming level, the strftime routine is what <EM>Alpine</EM>
uses to print the date.
If the Disable-Index-Locale-Dates option is set then this is equivalent
to SMARTDATES1.</DD>
  <DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD>
  <DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
  <DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD>
  <DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD>
  <DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD>
  <DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD>
  </DL>
</DD>

<DT>SMARTDATETIME alternatives</DT>
<DD>
There are several versions of SMARTDATETIME which are all very similar.
The ones which end in 24 use a 24-hour clock for Today's messages instead
of a 12-hour clock.
The other variation is
for the way they format dates far in the past.
SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings
to format the date string. It may end up formatting dates so that they look
like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
The feature
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>
may have an affect on the values of these tokens.
The possible choices are:
  <DL>
  <DT>SMARTDATETIME</DT> <DD>Locale specific. Control this with the
LC_TIME locale setting on a UNIX system. On Windows
the Regional Options control panel may be used to set the Short date
format. At the programming level, the strftime routine is what <EM>Alpine</EM>
uses to print the date.</DD>
  <DT>SMARTDATETIME</DT> <DD>If the option
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is not set
then this will be locale specific. Control this with the
LC_TIME locale setting on a UNIX system. On Windows
the Regional Options control panel may be used to set the Short date
format. At the programming level, the strftime routine is what <EM>Alpine</EM>
uses to print the date.
If the Disable-Index-Locale-Dates option is set then this is equivalent
to SMARTDATETIMES1.</DD>
  <DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD>
  <DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD>
  <DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD>
  <DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
  <DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD>
  <DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD>
  <DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD>
  <DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD>
  <DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD>
  <DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD>
  <DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD>
  <DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD>
  <DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD>
  </DL>
</DD>

<DT>DAYDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It looks like &quot;Sat, 23 Oct 1998&quot;.
This token is never converted in any locale-specific way.
</DD>

<DT>PREFDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the &quot;Date&quot; header field.
It is your operating system's idea of the preferred date representation for the current locale.
Internally it uses the %x version of the date from the strftime routine.
</DD>

<DT>PREFTIME</DT>
<DD>
This token represents the time at which the message was sent, according
to the &quot;Date&quot; header field.
It is the preferred time representation for the current locale.
Internally it uses the %X version of the time from the strftime routine.
</DD>

<DT>PREFDATETIME</DT>
<DD>
This token represents the date and time at which the message was sent, according
to the &quot;Date&quot; header field.
It is the preferred date and time representation for the current locale.
Internally it uses the %c version of the time from the strftime routine.
</DD>

<DT>DAY</DT>
<DD>
This token represents the day of the month on which the message was sent,
according to the &quot;Date&quot; header field.
For example, &quot;23&quot; or &quot;9&quot;.
</DD>

<DT>DAY2DIGIT</DT>
<DD>
This token represents the day of the month on which the message was sent,
according to the &quot;Date&quot; header field.
For example, &quot;23&quot; or &quot;09&quot;.
It is always 2 digits.
</DD>

<DT>DAYORDINAL</DT>
<DD>
This token represents the ordinal number which is the day of
the month on which the message was sent,
according to the &quot;Date&quot; header field.
For example, &quot;23rd&quot; or &quot;9th&quot;.
</DD>

<DT>DAYOFWEEK</DT>
<DD>
This token represents the day of the week on which the message was sent,
according to the &quot;Date&quot; header field.
For example, &quot;Sunday&quot; or &quot;Wednesday&quot;.
</DD>

<DT>DAYOFWEEKABBREV</DT>
<DD>
This token represents the day of the week on which the message was sent,
according to the &quot;Date&quot; header field.
For example, &quot;Sun&quot; or &quot;Wed&quot;.
</DD>

<DT>MONTHABBREV</DT>
<DD>
This token represents the month the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;Oct&quot;.
</DD>

<DT>MONTHLONG</DT>
<DD>
This token represents the month in which the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;October&quot;.
</DD>

<DT>MONTH</DT>
<DD>
This token represents the month in which the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;10&quot; or &quot;9&quot;.
</DD>

<DT>MONTH2DIGIT</DT>
<DD>
This token represents the month in which the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;10&quot; or &quot;09&quot;.
It is always 2 digits.
</DD>

<DT>YEAR</DT>
<DD>
This token represents the year the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;1998&quot; or &quot;2001&quot;.
</DD>

<DT>YEAR2DIGIT</DT>
<DD>
This token represents the year the message was sent, according
to the &quot;Date&quot; header field.
For example, &quot;98&quot; or &quot;01&quot;.
It is always 2 digits.
</DD>

<DT>TIME24</DT>
<DD>
This token represents the time at which the message was sent, according
to the &quot;Date&quot; header field.
There is no adjustment made for different time zones, so you'll get
the time the message was sent according to the time zone the sender
was in.
It has the format HH:MM. For example, &quot;17:28&quot;.
</DD>

<DT>TIME12</DT>
<DD>
This token represents the time at which the message was sent, according
to the &quot;Date&quot; header field.
This time is for a 12 hour clock.
It has the format HH:MMpm.
For example, &quot;5:28pm&quot; or &quot;11:13am&quot;.
</DD>

<DT>TIMEZONE</DT>
<DD>
This token represents the numeric timezone from
the &quot;Date&quot; header field.
It has the format [+-]HHMM. For example, &quot;-0800&quot;.
</DD>

</DL>

<P>
<H3><EM>Tokens Available Only for Index-Format</EM></H3>

<DL>
<DT>MSGNO</DT>
<DD>
This token represents the message's current position in the folder which,
of course, may change as the folder is sorted or new mail arrives.
</DD>

<DT>STATUS</DT>
<DD>
This token represents a three character wide field displaying various
aspects of the message's state.
The first character is either blank,
a '*' for message marked Important, or a '+' indicating a message
addressed directly to you (as opposed to your having received it via a
mailing list, for example).
When the feature
<A HREF="#mark-for-cc"><EM>mark-for-cc</EM></A>
is set, if the first character would have been
blank then it will instead be a '-' if the message is cc'd to you.
The second character is typically blank,
though the arrow cursor may occupy it if either the 
<A HREF="#assume-slow-link"><EM>assume-slow-link</EM></A>
or the
<A HREF="#force-arrow-cursor"><EM>force-arrow-cursor</EM></A> feature
is set (or you actually are on a slow link).
The third character is either D (Deleted),
A (Answered),
N (New), or blank.
<P>
If you are using a threaded view of the index and this message is at the
top of a collapsed portion of a thread,
then this token refers to all of the messages in the collapsed portion of
the thread instead of just the top message.
The first character will be a '*' if <EM>any</EM> of the messages in the thread
are marked Important, else a '+' if any of the messages are addressed
to you, else a '-' if any of the messages are cc'd to you.
The third character will be a 'D' if <EM>all</EM> of the messages
in the collapsed thread are marked deleted,
an 'A' if <EM>all</EM> of the messages
in the collapsed thread are marked answered,
it will be an 'N' if any of
the messages are undeleted and unseen, and it will be blank otherwise.
</DD>

<DT>FULLSTATUS</DT>
<DD>
This token represents a less abbreviated alternative
to the &quot;STATUS&quot; token.
It is six characters wide.
The first character is '+', '-', or blank, the
second blank, the third either '*' or blank, the fourth
N or blank,
the fifth A
or blank, and the sixth character is
either D or
blank.
<P>
If you are using a threaded view of the index and this message is at the
top of a collapsed portion of a thread,
then this token refers to all of the messages in the collapsed portion of
the thread instead of just the top message.
The first character is '+', '-', or blank depending on whether <EM>any</EM>
of the messages in the collapsed thread are addressed to you or cc'd to you.
The third character will be '*' if any of the messages are marked
Important.
The fourth character will be 'N' if all of the messages in the thread
are New, else 'n' if some of the messages in the thread are New, else blank.
The fifth character will be 'A' or 'a' or blank, and the sixth character
will be 'D' or 'd' or blank.
</DD>

<DT>IMAPSTATUS</DT>
<DD>
This token represents an even less abbreviated alternative to the
&quot;STATUS&quot; token.
It differs from &quot;FULLSTATUS&quot; in only the fourth character which is
an 'N' if the message is new to this folder since the last time
it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message
is new to the folder and has been viewed, a 'U' (Unseen) if the message is not 
new to the folder since it was last opened <EM>but</EM> has not been
viewed, or a blank if the message has been in the folder since it was
last opened and has been viewed.
<P>
If you are using a threaded view of the index and this message is at the
top of a collapsed portion of a thread,
then the fourth character will be
'N' if all of the messages in the thread are unseen and recent;
else 'n' if some of the messages in the thread are unseen and recent;
else 'U' if all of the messages in the thread are unseen and not recent;
else 'u' if some of the messages in the thread are unseen and not recent;
else 'R' if all of the messages in the thread are seen and recent;
else 'r' if some of the messages in the thread are seen and recent;
else blank.
</DD>

<DT>SHORTIMAPSTATUS</DT>
<DD>
This is the same as the last four of the six characters of IMAPSTATUS,
so the '+' To Me information will be missing.
</DD>

<DT>SIZE</DT>
<DD>
This token represents the total size, in bytes, of the message.
If a &quot;K&quot; (Kilobyte)
follows the number, the size is approximately 1,000
times that many bytes (rounded to the nearest 1,000).
If an &quot;M&quot; (Megabyte) follows the number, the size is approximately
1,000,000 times that many bytes.
Commas are not used in this field.
This field is seven characters wide, including the enclosing parentheses.
Sizes are rounded when &quot;K&quot; or &quot;M&quot; is present.
The progression of sizes used looks like:

<P>
<CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER>
<P>
</DD>

<DT>SIZECOMMA</DT>
<DD>
This token represents the total size, in bytes, of the message.
If a &quot;K&quot; (Kilobyte)
follows the number, the size is approximately 1,000
times that many bytes (rounded to the nearest 1,000).
If an &quot;M&quot; (Megabyte) follows the number, the size is approximately
1,000,000 times that many bytes.
Commas are used if the number shown is 1,000 or greater.
The SIZECOMMA field is one character wider than the SIZE field.
Sizes are rounded when &quot;K&quot; or &quot;M&quot; is present.
The progression of sizes used looks like:

<P>
<CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER>
<P>
</DD>

<DT>KSIZE</DT>
<DD>
This token represents the total size of the message, expressed in
kilobytes or megabytes, as most appropriate.
These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes.
The progression of sizes used looks like:

<P>
<CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER>
<P>
</DD>

<DT>SIZENARROW</DT>
<DD>
This token represents the total size, in bytes, of the message.
If a &quot;K&quot; (Kilobyte)
follows the number, the size is approximately 1,000
times that many bytes.
If an &quot;M&quot; (Megabyte) follows the number, the size is approximately
1,000,000 times that many bytes.
If a &quot;G&quot; (Gigabyte) follows the number, the size is approximately
1,000,000,000 times that many bytes.
This field uses only five characters of screen width, including the enclosing
parentheses.
The progression of sizes used looks like:

<P>
<CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER>
<P>
</DD>

<DT>DESCRIPSIZE</DT>
<DD>
This token is intended to represent a more useful description of the
message than just its size, but it isn't very useful at this point.
The plus sign in this view means there are attachments.
Note that including this token in
the &quot;Index-Format&quot; could slow down the
display a little while <EM>Alpine</EM> collects the necessary information.
</DD>

<DT>SUBJKEY</DT>
<DD>
This token is the same as the SUBJECT token unless keywords are set for
the message.
In that case, a list of keywords enclosed in braces will be prepended to
the subject of the message.
Only those keywords that you have defined in your
<A HREF="#keywords">Keywords</A> option
in Setup/Config are considered in the list.
In other words, keywords that have been set by some other means, perhaps
by another email program, won't show up unless included in
<A HREF="#keywords">Keywords</A>.
Having this set in the Index-Format will also cause the keywords to be
prepended to the subject in the MESSAGE TEXT screen.
If you have given a keyword a nickname
(<A HREF="#keywords"><EM>keywords</EM></A>), that nickname is displayed
instead of the actual keyword.
The <A HREF="#keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A>
option may be used to modify this token slightly.
It is also possible to color keywords in the index using the
Setup/Kolor screen.
</DD>

<DT>SUBJKEYINIT</DT>
<DD>
This token is the same as the SUBJKEY token except that instead of
prepending a list of keywords to the subject, a list of first initials
of keywords will be prepended instead.
For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM>
set (or Work and Now are the <EM>Alpine</EM> nicknames of keywords which are set)
then the SUBJKEY token would cause a result like
<P>
<CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
<P>
whereas the SUBJKEYINIT token would give
<P>
<CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
<P>
Only those keywords that you have defined in your
<A HREF="#keywords">Keywords</A> option
in Setup/Config are considered in the list.
In other words, keywords that have been set by some other means, perhaps
by another email program, won't show up unless included in
<A HREF="#keywords">Keywords</A>.
The <A HREF="#keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A>
option may be used to modify this token slightly.
It is also possible to color keywords in the index using the
Setup/Kolor screen.
</DD>

<DT>SUBJECTTEXT</DT>
<DD>
Same as SUBJECT but if there is room in the Subject field for more text,
the opening part of the text of the message is displayed after the subject.
The time needed to fetch the text may cause a performance problem
which can, of course, be avoided by using the SUBJECT version of
the Subject instead.
You may color this opening text differently by using the
<A HREF="#index-opening-color"><EM>Index Opening Color</EM></A> option available from
the Setup Kolor screen.
You may adjust the characters that are displayed between the Subject and the
opening text with the option
<A HREF="#opening-text-separator-chars"><EM>Opening-Text-Separator-Chars</EM></A>.
</DD>

<DT>SUBJKEYTEXT</DT>
<DD>
Same as SUBJKEY but with the opening message text.
</DD>

<DT>SUBJKEYINITTEXT</DT>
<DD>
Same as SUBJKEYINIT but with the opening message text.
</DD>

<DT>OPENINGTEXT</DT>
<DD>
This is similar to SUBJECTTEXT.
Instead of combining the Subject and the opening text in a single
field in the index screen this token allows you to allocate a
separate column just for the opening text of the message.
The time needed to fetch this text may cause a performance problem.
You may color this opening text differently by using the
<A HREF="#index-opening-color"><EM>Index Opening Color</EM></A> option available from
the Setup Kolor screen.
</DD>

<DT>OPENINGTEXTNQ</DT>
<DD>
This is very similar to OPENINGTEXT.
The NQ stands for No Quotes.
The only difference is that quoted text (lines beginning with &gt;) is deleted.
For some messages this may be confusing.
For example, a message might have a line preceding some quoted
text that reads something like &quot;On May 8th person A said.&quot;
That no longer makes sense after the quoted text is deleted and it
will appear that person A said whatever the text after the quote
is, even though that is really person B talking.
</DD>

<DT>KEY</DT>
<DD>
This is a space-delimited list of keywords that are set for the message.
Only those keywords that you have defined in your
<A HREF="#keywords">Keywords</A> option
in Setup/Config are considered in the list.
In other words, keywords that have been set by some other means, perhaps
by another email program, won't show up unless included in
<A HREF="#keywords">Keywords</A>.
If you have given a keyword a nickname
that nickname is displayed
instead of the actual keyword.
It is also possible to color keywords in the index using the
Setup/Kolor screen.
This token defaults to an arbitrary width of 5.
You should set it to whatever width suits you using something
like KEY(17) in the Index-Format.
</DD>

<DT>KEYINIT</DT>
<DD>
This is a list of keyword initials that are set for the message.
If you have given a keyword a nickname
the initial of that nickname
is displayed instead of the initial of the actual keyword.
It is also possible to color keyword initials in the index using the
Setup/Kolor screen.
This token defaults to an arbitrary width of 2.
You should set it to whatever width suits you using something
like KEYINIT(3) in the Index-Format.
</DD>

<DT>PRIORITY</DT>
<DD>
The X-Priority header is a non-standard header that is used in a
somewhat standard way by many mail programs.
<EM>Alpine</EM> expects the value of this header to be a digit with a value
from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
Since this priority is something that the sender sets it is only an indication
of the priority that the sender attaches to the mail and it is therefore almost
totally unreliable for use as a filtering criterion.
This token will display the numeric value of the priority if it is between
1 and 5.
It will be suppressed (blank) if the value is 3, which is normal priority.
It is also possible to set the color of the PRIORITY field.
By default the token is colored the same
as the index line it is part of.
You may set it to be another color with the 
<A HREF="#index-pri-color">Index Priority Colors</A> options available from
the Setup Kolor screen.
</DD>

<DT>PRIORITYALPHA</DT>
<DD>
This is a more verbose interpretation of the X-Priority field.
Once again nothing is displayed unless the value of the field
is 1, 2, 4, or 5.
The values displayed for those values are:
<P>
<TABLE>
<TR> <TD>1</TD> <TD>Highest</TD> </TR>
<TR> <TD>2</TD> <TD>High</TD> </TR>
<TR> <TD>4</TD> <TD>Low</TD> </TR>
<TR> <TD>5</TD> <TD>Lowest</TD> </TR>
</TABLE>
<P>
You may color this token with the
<A HREF="#index-pri-color">Index Priority Colors</A> options.
</DD>

<DT>PRIORITY!</DT>
<DD>
This is a one character, non-numeric version of the X-Priority field.
If the value of the X-Priority header is 1 or 2 an exclamation
point is displayed.
If the value is 4 or 5 a &quot;v&quot; (think down arrow) is displayed.
You may color this token with the
<A HREF="#index-pri-color">Index Priority Colors</A> options.
</DD>

<DT>ATT</DT>
<DD>
This is a one column wide field which represents the number of attachments
a message has. It will be blank if there are no attachments, a single
digit for one to nine attachments, or an asterisk for more than nine.
Note that including this token in
the &quot;Index-Format&quot; could slow down the
display a little while <EM>Alpine</EM> collects the necessary information.
</DD>

<DT>FROMORTO</DT>
<DD>
This token represents <EM>either</EM> the personal name (or email address) of
the person listed in the message's &quot;From:&quot; header
field, <EM>or</EM>, if that address is yours or one of your
<A HREF="#alt-addresses">alternate addresses</A>,
the first person specified in the
message's &quot;To:&quot; header field
with the prefix &quot;To: &quot; prepended.
If the from address is yours and there is also no &quot;To&quot; address,
<EM>Alpine</EM> will use the address on the &quot;Cc&quot; line.
If there is no address there, either, <EM>Alpine</EM> will look for a newsgroup name
from the &quot;Newsgroups&quot; header field and put
that after the &quot;To: &quot; prefix.
</DD>

<DT>FROMORTONOTNEWS</DT>
<DD>
This is almost the same as <EM>FROMORTO</EM>.
The difference is that newsgroups aren't considered.
When a message is from you, doesn't have a To or Cc, and does have
a Newsgroups header; this token will be your name instead of the name
of the newsgroup (like it would be with FROMORTO).
</DD>

<DT>TEXT</DT>
<DD>
This is a different sort of token.
It allows you to display a label within each index line.
It will be the same fixed text for each line.
It is different from all the other tokens in that there is no space column
displayed after this token.
Instead, it is butted up against the following field.
It also has a different syntax.
The text to display is given following a colon after the
word &quot;TEXT&quot;.
For example,
<P>
<CENTER><SAMP>TEXT:abc=</SAMP></CENTER>
<P>
would insert the literal text &quot;abc=&quot; (without the quotes)
into the index display line.
You must quote the text if it includes space characters, like
<P>
<CENTER><SAMP>TEXT:&quot;abc&nbsp;=&nbsp;&quot;</SAMP></CENTER>
<P>
</DD>

<DT>HEADER</DT>
<DD>
This allows you to display the text from a particular header line in the
message.
The syntax for this token is substantially different from all the others
in order that you might be able to display a portion of the text following
a particular header.
The header name you are interested in is given following a colon
after the word &quot;HEADER&quot;.
For example,
<P>
<CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER>
<P>
would display the text of the X-Spam header, if any.
Like for other index tokens a width field may (and probably should)
follow this.
<P>
<CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER>
<P>
displays the first ten characters of the X-Spam header.
Unlike other index tokens, the syntax for HEADER is more flexible.
An optional second argument comes after a comma inside the parentheses.
It specifies the &quot;field&quot; number.
By default, the field separator is a space character.
No extra space characters are allowed in the argument list.
<P>
<CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER>
<P>
would display the second field, left-justified, in a 10 character
wide field.
The second field would consist of all the text after the first space
up to the next space or the end of the header.
The default field number is zero, which stands for the entire line.
There is also an optional third argument which is a list of field
separators. It defaults to a space character.
The example
<P>
<CENTER><SAMP>HEADER:X-Spam(10,2,:%&nbsp;)</SAMP></CENTER>
<P>
would cause the field separators to be any of colon, percent,
or space (there is a space character between the percent and the
right parenthesis).
The first field runs from the start of the header value up to the first
colon, percent, or space; the second goes from there to the next; and so on.
In order to use a comma character as a field separator you must escape
it by preceding it with a backslash (&#92;).
The same is true of the backslash character itself.
There is one further optional argument.
It is an R or an L to specify right or left adjustment of the text
within the field.
The default is to left justify, however if you are displaying numbers
you might prefer to right justify.
<P>
Here's an example of a SpamAssassin header.
The exact look of the header will vary, but if your incoming mail
contains headers that look like the following
<P>
<CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
<P>
you might want to display the hits value.
The first field starts with the Y in Yes.
To get what you're interested in you might use &quot;=&quot; and
space as the field separators and display the third field, like
<P>
<CENTER><SAMP>HEADER:X-Spam-Status(4,3,=&nbsp;)</SAMP></CENTER>
<P>
or maybe you would break at the dot instead
<P>
<CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER>
<P>
Another example we've seen has headers that look like
<P>
<CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
<P>
Because there are two equals and a comma before the 7% and a comma
after it, the token
<P>
<CENTER><SAMP>HEADER:X-Spam-Status(3,4,=&#92;,,R)</SAMP></CENTER>
<P>
should display the probability (for example 7% or 83%) right justified
in a 3-wide field.
</DD>


<DT>ARROW</DT>
<DD>
This gives an alternative way to display the current message in the
MESSAGE INDEX screen.
Usually the current message is indicated by the line being shown in
reverse video.
Instead, if the ARROW token is included in your Index-Format,
the current line will include an &quot;arrow&quot; that
looks like
<P>
<CENTER><SAMP>-&gt;</SAMP></CENTER>
<P>
in the ARROW token's field.
For all of the non-current messages, the ARROW field will be filled
with blanks.
If you use the fixed-field width feature the length of the &quot;arrow&quot;
may be adjusted.
The arrow will be drawn as width-1 dashes followed by a greater than sign.
For example, if you use ARROW(3) you will get
<P>
<CENTER><SAMP>--&gt;</SAMP></CENTER>
<P>
and ARROW(1) will give you just
<P>
<CENTER><SAMP>&gt;</SAMP></CENTER>
<P>
It is also possible to set the color of the ARROW field.
By default (and for non-current messages) the arrow is colored the same
as the index line it is part of.
You may set it to be another color with the 
<A HREF="#index-arrow-color">Index Arrow Color</A> option available from
the Setup Kolor screen.
</DD>

<DT>SCORE</DT>
<DD>
This gives the
score
of each message.
This will be six columns wide to accommodate the widest possible score.
You will probably want to use the Index-Format fixed-field width feature
to limit the width of the field to the widest score that
you use (e.g. SCORE(3) if your scores are always between 0 and 999).
If you have not defined any score rules the scores will all be zero.
If any of your score rules contain AllText or BodyText patterns
then including SCORE in the Index-Format
may slow down the display of the MESSAGE INDEX screen.
</DD>
</DL>

<P>
<H3><EM>Tokens Available for all but Index-Format</EM></H3>

<DL>
<DT>CURNEWS</DT>
<DD>
This token represents the current newsgroup if there is one.
For example, &quot;comp.mail.pine&quot;.
</DD>

<DT>MSGID</DT>
<DD>
This token represents the message ID of the message.
This token does not work with Filter Rule folder names.
</DD>

<DT>CURDATE</DT>
<DD>
This token represents the current date.
It has the format MMM DD. For example, &quot;Oct 23&quot;.
</DD>

<DT>CURDATEISO</DT>
<DD>
This token represents the current date.
It has the format YYYY-MM-DD. For example, &quot;1998-10-23&quot;.
</DD>

<DT>CURDATEISOS</DT>
<DD>
This token represents the current date.
It has the format YY-MM-DD. For example, &quot;98-10-23&quot;.
</DD>

<DT>CURPREFDATE</DT>
<DD>
This token represents the current date.
It is your operating system's idea of the preferred date representation for the current locale.
Internally it uses the %x version of the date from the strftime routine.
</DD>

<DT>CURPREFTIME</DT>
<DD>
This token represents the current time.
It is the preferred time representation for the current locale.
Internally it uses the %X version of the time from the strftime routine.
</DD>

<DT>CURPREFDATETIME</DT>
<DD>
This token represents the current date and time.
It is the preferred date and time representation for the current locale.
Internally it uses the %c version of the time from the strftime routine.
</DD>

<DT>CURTIME24</DT>
<DD>
This token represents the current time.
It has the format HH:MM. For example, &quot;17:28&quot;.
</DD>

<DT>CURTIME12</DT>
<DD>
This token represents the current time.
This time is for a 12 hour clock.
It has the format HH:MMpm.
For example, &quot;5:28pm&quot; or &quot;11:13am&quot;.
</DD>

<DT>CURDAY</DT>
<DD>
This token represents the current day of the month.
For example, &quot;23&quot; or &quot;9&quot;.
</DD>

<DT>CURDAY2DIGIT</DT>
<DD>
This token represents the current day of the month.
For example, &quot;23&quot; or &quot;09&quot;.
It is always 2 digits.
</DD>

<DT>CURDAYOFWEEK</DT>
<DD>
This token represents the current day of the week.
For example, &quot;Sunday&quot; or &quot;Wednesday&quot;.
</DD>

<DT>CURDAYOFWEEKABBREV</DT>
<DD>
This token represents the current day of the week.
For example, &quot;Sun&quot; or &quot;Wed&quot;.
</DD>

<DT>CURMONTH</DT>
<DD>
This token represents the current month.
For example, &quot;10&quot; or &quot;9&quot;.
</DD>

<DT>CURMONTH2DIGIT</DT>
<DD>
This token represents the current month.
For example, &quot;10&quot; or &quot;09&quot;.
It is always 2 digits.
</DD>

<DT>CURMONTHLONG</DT>
<DD>
This token represents the current month.
For example, &quot;October&quot;.
</DD>

<DT>CURMONTHABBREV</DT>
<DD>
This token represents the current month.
For example, &quot;Oct&quot;.
</DD>

<DT>CURYEAR</DT>
<DD>
This token represents the current year.
For example, &quot;1998&quot; or &quot;2001&quot;.
</DD>

<DT>CURYEAR2DIGIT</DT>
<DD>
This token represents the current year.
For example, &quot;98&quot; or &quot;01&quot;.
It is always 2 digits.
</DD>

<DT>LASTMONTH</DT>
<DD>
This token represents last month.
For example, if this is November (the 11th month),
it is equal to &quot;10&quot; or if this is October (the 10th month),
it is &quot;9&quot;.
It is possible that this and the other tokens beginning with LASTMONTH
below could be useful when used with a Filtering Rule that
has the &quot;Beginning of Month&quot; option set.
</DD>

<DT>LASTMONTH2DIGIT</DT>
<DD>
This token represents last month.
For example, if this is November (the 11th month),
it is equal to &quot;10&quot; or if this is October (the 10th month),
it is &quot;09&quot;.
It is always 2 digits.
</DD>

<DT>LASTMONTHLONG</DT>
<DD>
This token represents last month.
For example, if this is November the value is &quot;October&quot;.
</DD>

<DT>LASTMONTHABBREV</DT>
<DD>
This token represents last month.
For example, if this is November the value is &quot;Oct&quot;.
</DD>

<DT>LASTMONTHYEAR</DT>
<DD>
This token represents what the year was a month ago.
For example, if this is October, 1998, it is &quot;1998&quot;.
If this is January, 1998, it is &quot;1997&quot;.
</DD>

<DT>LASTMONTHYEAR2DIGIT</DT>
<DD>
This token represents what the year was a month ago.
For example, if this is October, 1998, it is &quot;98&quot;.
If this is January, 1998, it is &quot;97&quot;.
</DD>

<DT>LASTYEAR</DT>
<DD>
This token represents last year.
For example, if this is 1998, it equals &quot;1997&quot;.
It is possible that this
could be useful when used with a Filtering Rule that
has the &quot;Beginning of Year&quot; option set.
</DD>

<DT>LASTYEAR2DIGIT</DT>
<DD>
This token represents last year.
For example, if this is 1998, it equals &quot;97&quot;.
It is always 2 digits.
</DD>

<DT>ROLENICK</DT>
<DD>
This token represents the nickname of the
role currently being used.  If no role is being used,
then no text will be printed for this token.
This token does not work with Filter Rule folder names.
</DD>
</DL>

<P>
<H3><EM>Token Available Only for Reply-Leadin</EM></H3>
See the help for the
<A HREF="#reply-leadin"><EM>Reply-Leadin</EM></A> option,
to see why you might want to use this.
Since the <EM>Reply-Leadin</EM> contains free text this token
must be surrounded by underscores when used.

<DL>
<DT>NEWLINE</DT>
<DD>
This is an end of line marker.
</DD>
</DL>
<P>
<H3><EM>Token Available Only for Templates and Signatures</EM></H3>

<DL>
<DT>CURSORPOS</DT>
<DD>
This token is different from the others.
When it is replaced it is replaced with nothing, but it sets a <EM>Alpine</EM>
internal variable which tells the composer to start with the cursor
positioned at the position where this token was.
If both the template file and the signature file contain
a &quot;CURSORPOS&quot; token, then the position in the template file
is used.
If there is a template file and neither it nor the signature file contains
a &quot;CURSORPOS&quot; token, then the cursor is positioned
after the end of the contents of the
template file when the composer starts up.
</DD>
</DL>

<H2><A NAME="reply-token-conditionals"></A>Conditional Inclusion of Text for Reply-Leadin, Signatures, and Templates</H2>

Conditional text inclusion may be used with
the <A HREF="#reply-leadin"><EM>Reply-Leadin</EM></A> option,
in signature files, and in template files used in
roles.
It may <EM>not</EM> be used with the
<EM>Index-Format</EM> option.

<P>
There is a limited if-else capability for including text.
The if-else condition is based
on whether or not a given token would result in replacement text you
specify.
The syntax of this conditional inclusion is
<P>
<CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
<P>
The left parenthesis must follow the underscore immediately, with no
intervening space.
It means the token is expanded and the results of that expansion are
compared against the &quot;match_this&quot; argument.
If there is an exact match, then the &quot;if_matched&quot; text is used
as the replacement text.
Otherwise, the &quot;if_not_matched&quot; text is used.
One of the most useful values for the &quot;match_this&quot; argument is
the empty string, &quot;&quot;.
In that case the expansion is compared against the empty string.
<P>
Here's an example to make it clearer.
This text could be included in one of your template files:
<P>
<CENTER><SAMP>_NEWS_(&quot;&quot;, &quot;I'm replying to email&quot;,&quot;I'm replying to news&quot;)</SAMP></CENTER>
<P>
If that is included in a template file which you are using while replying
to a message (because you chose to use the role it was part of),
and that message has a newsgroup header and a newsgroup in that header,
then the text
<P>
<CENTER><SAMP>I'm replying to news</SAMP></CENTER>
<P>
will be included in the message you are about to compose.
On the other hand, if the message you are replying to does not have
a newsgroup, then the text
<P>
<CENTER><SAMP>I'm replying to email</SAMP></CENTER>
<P>
would be included instead.
This would also work in signature files and in
the &quot;Reply-Leadin&quot; option.
If the &quot;match_this&quot;, &quot;if_matched&quot;,
or &quot;if_not_matched&quot; arguments contain
spaces, parentheses, or commas;
they have to be quoted with double quotation marks (like in the example
above).
If you want to include a literal quote in the text you must escape the
quote by preceding it with a backslash character.
If you want to include a literal backslash character you must escape it
by preceding it with another backslash.
<P>
The comma followed by &quot;if_not_matched&quot; is optional.
If there is no &quot;if_not_matched&quot;
present then no text is included if the not_matched case is true.
Here's another example:
<P>
<CENTER><SAMP>_NEWS_(&quot;&quot;, &quot;&quot;, &quot;This msg was seen in group: _NEWS_.&quot;)</SAMP></CENTER>
<P>
Here you can see that tokens may appear in the arguments.
The same is true for tokens with the conditional parentheses.
They may appear in arguments,
though you do have to be careful to get the quoting and escaping of
nested double quotes correct.
If this was in the signature file being used and you were replying to a message
sent to comp.mail.pine the resulting text would be:
<P>
<CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
<P>
If you were replying to a message which wasn't sent to any newsgroup the
resulting text would be a single blank line.
The reason you'd get a blank line is because the end of the line is
outside of the conditional, so is always included.
If you wanted to get rid of that blank line you could do so by moving
the end of line inside the conditional.
In other words, it's ok to have multi-line
&quot;if_matched&quot; or &quot;if_not_matched&quot; arguments.
The text just continues until the next double quotation, even if it's not
on the same line.
<P>
Here's one more (contrived) example illustrating a matching argument
which is not the empty string.
<P>
<CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
<P>
If this was the value of your &quot;Reply-Leadin&quot; option and you
were replying to
a message which was sent today, then the value of the &quot;Reply-Leadin&quot;
would be
<P>
<CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
<P>
But if you were replying to a message sent on Oct. 27 (and that wasn't
today) you would get
<P>
<CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
<P>

<H2><A NAME="per-server-ldap-config"></A>Per Server Directory Configuration</H2>

This is only available if <EM>Alpine</EM> was built with LDAP support.
If that's the case, there will be a Directory option underneath the Setup
command on the Main Menu.
Each server that is defined there has several configuration variables
which control the behavior when using it.

<DL COMPACT>

<DT> <A NAME="ldap-server"><EM>ldap-server</EM></A>

<DD> This is the name of the host where an LDAP server is running.
<P>
To find out whether your organization has its own LDAP server, 
contact its computing support staff.
<P>

<DT> <A NAME="search-base"><EM>search-base</EM></A>

<DD> This is the search base to be used on this server.
It functions as a filter 
by restricting your searches in the LDAP server database
to the specified contents of the specified fields.
Without it, searches submitted to this directory server may fail.
It might be something like:

<PRE>
      O = &lt;Your Organization Name&gt;, C = US
</PRE>

or it might be blank.  
(Some LDAP servers actually ignore anything specified here.)
<P>

If in doubt what parameters you should specify here, 
contact the maintainers of the LDAP server.
<P>

<DT> <A NAME="port"><EM>port</EM></A>

<DD> This is the TCP port number to be used with this LDAP server.
If you leave this blank port <CODE>389</CODE> will be used.
<P>

<DT> <A NAME="ldap-nickname"><EM>nickname</EM></A>

<DD> This is a nickname to be used in displays.
If you don't supply a nickname the server name from
&quot;ldap-server&quot; will be used instead.
This option is strictly for your convenience.
<P>

<DT> <A NAME="use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A>

<DD> Set this feature to have lookups done to this server implicitly from
the composer.
If an address doesn't look like a fully-qualified address, it will be looked
up in your address books, and if it doesn't match a nickname there, then it
will be looked up on the LDAP servers which have this feature set.
The lookups will also be done when using the address completion feature
(TAB command) in the composer if any of the serves have this feature set.
Also see the LDAP feature
<A HREF="#lookup-addrbook-contents"><EM>lookup-addrbook-contents</EM></A>
and the Setup/Config feature
<A HREF="#ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A>.
<P>

<DT> <A NAME="lookup-addrbook-contents"><EM>lookup-addrbook-contents</EM></A>

<DD> Normally implicit LDAP lookups from the composer are done only for the
strings you type in from the composer screen. In other words, you type in
something in the To or CC field and press return, then the string is looked up.
First that string is looked up in your address books. If a match is found
there, then the results of that match are looked up again. If you place
a string in your address book that you want to have looked up on the LDAP
directory server, you need to turn on this feature. If you set this feature
for a server, you almost always will also want to set the
<A HREF="#use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A>
feature.
An example might serve to best illustrate this feature.
<P>
If an LDAP lookup of &quot;William Clinton&quot; normally returns an
entry with an
address of pres@whitehouse.gov, then you might put an entry in your address
book that looks like:
<PRE>
    Nickname     Address
    bill         &quot;William Clinton&quot;
</PRE>
Now, when you type &quot;bill&quot; into an
address field in the composer <EM>Alpine</EM> will
find the &quot;bill&quot; entry in your address book.
It will replace &quot;bill&quot; with
&quot;William Clinton&quot;.
It will then search for an entry with that nickname
in your address book and not find one. If this feature
is set, <EM>Alpine</EM> will then attempt to lookup
&quot;William Clinton&quot; on the LDAP server and find the entry with address
pres@whitehouse.gov.
<P>
A better way to accomplish the same thing is probably to use the feature
<A HREF="#save-search-criteria-not-result"><EM>save-search-criteria-not-result</EM></A>.
<P>

<DT> <A NAME="save-search-criteria-not-result"><EM>save-search-criteria-not-result</EM></A>

<DD> Normally when you save the results of an LDAP directory lookup to your
address book the <EM>results</EM> of the lookup are saved.
If this feature is set
and the entry being saved was found on this directory server, then the
search <EM>criteria</EM> is saved instead of the <EM>results</EM> of the search.
When this address book entry is used in the future, instead of copying
the results from the address book the directory lookup will be done again.
This could be useful if the copied result might become stale because the data on
the directory server changes (for example, the entry's email address changes).
You probably don't want to set this feature if the server is at all slow or
unreliable.
<P>
The way this actually works is that instead of saving the email address
in your address book, <EM>Alpine</EM> saves enough
information to look up the same directory entry again.
In particular, it saves the server name and the
distinguished name of the entry.
It's possible that the server administrators
might change the format of distinguished names on the server, or that the
entry might be removed from the server. If <EM>Alpine</EM> notices this, you will be warned
and a backup copy of the email address will be used. You may want to create
a new entry in this case, since you will get the annoying warning every
time you use the old entry. You may do that by Saving the entry to a new
nickname in the same address book. You will be asked whether or not you
want to use the backup email address.
<P>
A related feature in the Setup/Config screen is
<A HREF="#ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A>.
<P>

<DT> <A NAME="disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A>

<DD> Spaces in your input are normally handled specially.
Each space character is replaced
by
<PRE>
     * &lt;SPACE&gt;
</PRE>
in the search query (but not by &quot;* &lt;SPACE&gt; *&quot;).
The reason this is done is so the input string
<PRE>
     Greg Donald
</PRE>
(which is converted to &quot;Greg* Donald&quot;) will match
the names &quot;Greg Donald&quot;,
&quot;Gregory Donald&quot;, &quot;Greg F. Donald&quot;, and
&quot;Gregory F Donald&quot;; but it won't match &quot;Greg McDonald&quot;.
If the &quot;Search-Rule&quot; you were using was &quot;begins-with&quot;,
then it would also match the name &quot;Greg Donaldson&quot;.
<P>
Turning on this feature will disable this substitution.
<P>

<DT> <A NAME="search-type"><EM>search-type</EM></A>

<DD> This affects the way that LDAP searches are done.
In particular, this tells the server where to look for the string to be matched.
If set to &quot;name&quot; then the string that is being searched for will
be compared with the string in the
&quot;Name&quot; field on the server
(technically, it is the &quot;commonname&quot; field on the server).
&quot;Surname&quot; means we're looking for a
match in the &quot;Surname&quot; field on the
server (actually the &quot;sn&quot; field).
&quot;Givenname&quot; really is &quot;givenname&quot;
and &quot;email&quot; is the electronic mail address (this is actually the field
called &quot;mail&quot; or &quot;electronicmail&quot; on the server).
The other three types are combinations of
the types listed so far. &quot;Name-or-email&quot;
means the string should appear
in either the &quot;name&quot; field OR the &quot;email&quot; field.
Likewise, &quot;surname-or-givenname&quot;
means &quot;surname&quot; OR &quot;givenname&quot;
and &quot;sur-or-given-or-name-or-email&quot; means the obvious thing.
<P>
This search <EM>type</EM> is combined with the
search <A HREF="#search-rule"><EM>rule</EM></A>
to form the actual search query.
<P>
The usual default value for this
option is &quot;sur-or-given-or-name-or-email&quot;.
This type of search may be slow on some servers.
Try &quot;name-or-email&quot;, which is often
faster, or just &quot;name&quot; if the performance seems to be a problem.
<P>
Some servers have been configured with different attribute names for
these four fields.
In other words, instead of using the attribute name &quot;mail&quot;
for the email address field, the server might be configured to use something
else, for example, &quot;rfc822mail&quot; or &quot;internetemailaddress&quot;.
<EM>Alpine</EM> can be configured to use these different attribute names by using
the four per-server configuration options:
<P><UL>
<LI><A HREF="#email-attribute"><EM>email-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#name-attribute"><EM>name-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#surname-attribute"><EM>surname-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#givenname-attribute"><EM>givenname-attribute</EM></A>
</UL>
<P>

<DT> <A NAME="search-rule"><EM>search-rule</EM></A>

<DD> This affects the way that LDAP searches are done.
If set to &quot;equals&quot; then
only exact matches count.
&quot;Contains&quot; means that the string you type in
is a substring of what you are matching against.
&quot;Begins-with&quot; and &quot;ends-with&quot;
mean that the string starts or ends with the string you type in.
<P>
Spaces in your input are normally handled specially, but you can turn that
special handling off with the
<A HREF="#disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A>
feature.
<P>
The usual default value for this option is <EM>begins-with</EM>.
<P>

<DT> <A NAME="email-attribute"><EM>email-attribute</EM></A>

<DD> This is the name of the attribute which is searched for when looking for
an email address. The default value for this option is &quot;mail&quot; or
&quot;electronicmail&quot;.
If the server you are using uses a different attribute name for the email
address, put that attribute name here.
<P>
This will affect the search filter used if your Search-Type is one that
contains a search for &quot;email&quot;.
It will also cause the attribute value matching this attribute name to be used
as the email address when you look up an entry from the composer.
<P>

<DT> <A NAME="name-attribute"><EM>name-attribute</EM></A>

<DD> This is the name of the attribute which is searched for when looking for
the name of the entry. The default value for this option is &quot;cn&quot;, which
stands for common name.
If the server you are using uses a different attribute name for the name,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for &quot;name&quot;.
<P>

<DT> <A NAME="surname-attribute"><EM>surname-attribute</EM></A>

<DD> This is the name of the attribute which is searched for when looking for
the surname of the entry. The default value for this option is &quot;sn&quot;.
If the server you are using uses a different attribute name for the surname,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for &quot;surname&quot;.
<P>

<DT> <A NAME="givenname-attribute"><EM>givenname-attribute</EM></A>

<DD> This is the name of the attribute which is searched for when looking for
the given name of the entry. The default value for this option is &quot;givenname&quot;.
If the server you are using uses a different attribute name for the given name,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for &quot;givenname&quot;.
<P>

<DT> <A NAME="timelimit"><EM>timelimit</EM></A>

<DD> This places a limit on the number of seconds the LDAP search will continue.
The default is 30 seconds. A value of 0 means no limit. Note that some servers
may place limits of their own on searches.
<P>

<DT> <A NAME="sizelimit"><EM>sizelimit</EM></A>

<DD> This places a limit on the number of entries returned by the LDAP server.
A value of 0 means no limit. The default is 0. Note that some servers
may place limits of their own on searches.
<P>

<DT> <A NAME="custom-search-filter"><EM>custom-search-filter</EM></A>

<DD> This one is for advanced users only! If you define this, then the
<A HREF="#search-type"><EM>search-type</EM></A>
and
<A HREF="#search-rule"><EM>search-rule</EM></A>
defined are both ignored.
However, the feature
<A HREF="#disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A>
is still in effect.
That is, the space substitution will take place even in a custom filter unless
you disable it.
<P>
If your LDAP service stops working and you suspect it might be because
of your custom filter, just delete this filter and try using the
<EM>search-type</EM> and <EM>search-rule</EM> instead.
Another option that sometimes causes trouble is the
<A HREF="#search-base"><EM>search-base</EM></A> option.
<P>
This variable may be set to the string representation of an LDAP search
filter (see RFC1960). In the places where you want the address string to be
substituted in, put a '%s' in this filter string. Here are some examples:
<P>
A &quot;Search-Type&quot; of &quot;name&quot; with &quot;Search-Rule&quot; of &quot;begins-with&quot;
is equivalent to the &quot;custom-search-filter&quot;
<PRE>
     (cn=%s*)
</PRE>
When you try to match against the string &quot;string&quot; the program replaces
the &quot;%s&quot; with &quot;string&quot; (without the quotes). You may have multiple &quot;%s&quot;'s and
they will all be replaced with the string. There is a limit of 10 &quot;%s&quot;'s.
<P>
A &quot;Search-Type&quot; of &quot;name-or-email&quot; with &quot;Search-Rule&quot;
of &quot;contains&quot; is equivalent to
<PRE>
     (|(cn=*%s*)(mail=*%s*))
</PRE>
<P>
If your server uses a different attribute <EM>name</EM> than
<EM>Alpine</EM> uses by default,
(for example, it uses &quot;rfc822mail&quot; instead of &quot;mail&quot;),
then you may be able to use one or more of the four attribute configuration
options instead of defining a custom filter:
<P><UL>
<LI><A HREF="#email-attribute"><EM>email-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#name-attribute"><EM>name-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#surname-attribute"><EM>surname-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#givenname-attribute"><EM>givenname-attribute</EM></A>
</UL>

</DL>
<P>

<H2><A NAME="color-config"></A>Color Configuration</H2>

If the terminal or terminal emulator you are using is capable of using
color (see <A HREF="#color-style"><EM>color-style</EM></A> option),
or if you are using <EM>PC-Alpine</EM>, then it is possible to
set up <EM>Alpine</EM> so that various parts of the display will be
shown in colors you configure.
This is done using the Setup Color screen.
The Setup Color screen is divided into five broad sections: Options,
General Colors, Index Colors, Header Colors, and Keyword Colors.
In addition to these five categories you may also color lines in the
MESSAGE INDEX screen by configuring the
<A HREF="#index-color-config">Index Line Color</A>.
<P>
Each color is defined as a foreground color (the color of the actual text)
and a background color (the color of the area behind the text).
<P>
<H3><A NAME="color-options"></A>Color Options</H3>

<DL>

<DT> <A NAME="cur-il-style"><EM>current-indexline-style</EM></A>
<DD> 
This option affects the colors used to display the current line in the
MESSAGE INDEX screen.
If you do not have
<A HREF="#index-color-config">Index Line Colors</A>
defined, then this option will have no effect in the index.
Those Rules may be defined by going to the Setup/Rules/Indexcolor screen.
<P>
If the option
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is turned on and the
<A HREF="#incoming-unseen-color"><EM>Incoming Unseen Color</EM></A>
is set to something other than the default, then
this option also affects the color used to display the current folder
in the Incoming FOLDER LIST screen.

<P>
The available options include:
<P>

<DL>
<DT>flip-colors</DT>
<DD>This is the default.
If an index line is colored because it matches one of your
Index Color Rules, then its colors will be reversed when it is the currently
highlighted line.
For example, if the line is normally red text on a blue background, then
when it is the current line it will be drawn as blue text on a red background.
<P>
The rest of the option values all revert to this flip-colors behavior if
there is no Reverse Color defined.
</DD>

<DT>reverse</DT>
<DD>With this option the Reverse color is always used to highlight the
current line.
</DD>

<DT>reverse-fg</DT>
<DD>The foreground part of the Reverse Color is used to highlight
the current line.
If this would cause the text to be unreadable (because the foreground and
background colors are the same) or if it would cause no change in the
color of the index line, then the colors are flipped instead.
<P>
Some people think this works particularly well if you use different
background colors to emphasize &quot;interesting&quot; lines,
but always with the same Normal foreground color,
and you use a different foreground color for the Reverse Color.
</DD>

<DT>reverse-fg-no-ambiguity</DT>
<DD>With the &quot;reverse-fg&quot; rule above, it is possible that
the resulting color will be exactly the same as the regular Reverse
Color.
That can lead to some possible confusion because an
&quot;interesting&quot;
line which is the current line will be displayed exactly the same as a
non-interesting line which is current.
You can't tell whether the line is just a regular current line or if it is
an &quot;interesting&quot; current line by looking at the color.
Setting the option to this value removes that ambiguity.
It is the same as the &quot;reverse-fg&quot; setting unless the resulting
interesting current line would look just like a non-interesting current line.
In that case, the interesting line's colors are simply flipped (like in the
default behavior).
<P>
As an alternative way to preserve the line's interestingness in this case,
you may find that using both a different foreground and a different
background color for the interesting line will help.
</DD>

<DT>reverse-bg</DT>
<DD>The background part of the Reverse Color is used to highlight
the current line.
If this would cause the text to be unreadable (because the foreground and
background colors are the same) or if it would cause no change in the
color of the index line, then the colors are flipped instead.
<P>
Some people think this works particularly well if you use different
foreground colors to emphasize &quot;interesting&quot; lines,
but always with the same Normal background color,
and you use a different background color for the Reverse Color.
</DD>

<DT>reverse-bg-no-ambiguity</DT>
<DD>As with the &quot;reverse-fg&quot; case, the &quot;reverse-bg&quot;
rule may also result in a color which is exactly the same as the regular
Reverse Color.
Setting the option to this value removes that ambiguity.
It is the same as the &quot;reverse-bg&quot; setting unless the resulting
current line has the same color as the Reverse Color.
In that case, the interesting line's colors are simply flipped (like in the
default behavior).
</DD>
</DL>

<DT> <A NAME="titlebar-style"><EM>titlebar-color-style</EM></A>
<DD> 
This option affects the colors used to display the titlebar (the top
line on the screen) when viewing a message.

<P>
The available options include:
<P>

<DL>
<DT>default</DT>
<DD>The color of the titlebar will be the color you set for the
<A HREF="#title-color"><EM>Title Color</EM></A>.
The Title Color may be set by using the
</DD>

<DT>indexline</DT>
<DD>The color of the titlebar will be the same as the color of the
index line corresponding to the message being viewed.
The rules which determine what color the index line will be may be set
up by going to the Setup/Rules/Indexcolor screen.
If the index line for a message is not colored explicitly by the
Indexcolor rules, then the titlebar will be colored the same as for
the &quot;default&quot; option above (which is not the same color that
the index line itself will have).
</DD>

<DT>reverse-indexline</DT>
<DD>This is similar to the &quot;indexline&quot; option except the
foreground and background colors from the corresponding index line will
be reversed.
For example, if the index line color is red letters on a white background,
then the titlebar will be white letters on a red background.
If the index line for a message is not colored explicitly by the
Indexcolor rules, then the titlebar will be colored the same as for
the &quot;default&quot; option above (which is not the same color that
the index line itself will have).
</DD>
</DL>

</DL>

<P>
<H3><A NAME="general-colors"></A>General Colors</H3>

<DL COMPACT>

<DT> <A NAME="normal-color"><EM>Normal Color</EM></A>

<DD> This is the color which most of the screen is painted in.
By default this color is black characters on a white background.
<P>

<DT> <A NAME="reverse-color"><EM>Reverse Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for reverse video characters.
Actually, the name is misleading. This used to be reverse video and so
the name remains. It is still used to highlight certain parts of the
screen but the color may be set to whatever you'd like.
<P>

<DT> <A NAME="title-color"><EM>Title Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for the titlebar (the top line on the
screen).
By default, the Title Color is black characters on a yellow background.
The actual titlebar color may be different from the Title Color if
the option
<A HREF="#titlebar-color-style"><EM>titlebar-color-style</EM></A>
is set to some value other than the default.
It may also be different if the current folder is closed and the
<A HREF="#title-closed-color">Title Closed Color</A>
is set to something different from the Title Color.
<P>

<DT> <A NAME="title-closed-color"><EM>Title-closed Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for the titlebar (the top line on the
screen) when the current folder is closed.
By default, the Title Color Closed Color is white characters on a red background.
<P>

<DT> <A NAME="status-color"><EM>Status Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for messages written to the status
message line near the bottom of the screen.
By default, the Status Color is the same as the Reverse Color.
<P>

<DT> <A NAME="keylabel-color"><EM>KeyLabel Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for the labels of the commands in the
two-line menu at the bottom of the screen.
The label is the long name, for example, &quot;PrevMsg&quot;.
By default, the KeyLabel Color is the same as the Normal Color.
<P>
WARNING: Some terminal emulators have the property that the screen will scroll
down one line whenever a character is written to the character cell in the
lower right corner of the screen.
<EM>Alpine</EM> can usually avoid writing a character in that corner of the screen.
However, if you have defined a KeyLabel Color then <EM>Alpine</EM> does have to write
a character in that cell in order to color the cell correctly.
If you find that your display sometimes scrolls up a line this could be
the problem.
The most obvious symptom is probably that the titlebar at the top of the
screen scrolls off the screen.
Try setting KeyLabel Color to Default to see if that fixes the problem.
<P>

<DT> <A NAME="keyname-color"><EM>KeyName Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for the names of the commands in the
two-line menu at the bottom of the screen.
The KeyName is the shorter name in the menu. For example, the &quot;W&quot;
before the &quot;WhereIs&quot;.
By default, the KeyName Color is the same as the Normal Color.
<P>

<DT> <A NAME="selectable-item-color"><EM>Selectable-item Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for displaying selectable items, such
as URLs.
By default, the Selectable-item Color is the same as the Normal Color, except
it is also Bold.
<P>

<DT> <A NAME="meta-message-color"><EM>Meta-message Color</EM></A>

<DD> The color <EM>Alpine</EM> uses in the MESSAGE TEXT screen for messages to you
that aren't part of the message itself.
By default, the Meta-Message Color is black characters on a yellow background.
<P>

<DT> <A NAME="quote-colors"><EM>Quote Colors</EM></A>

<DD> The colors <EM>Alpine</EM> uses for coloring quoted text in the
MESSAGE TEXT screen.
If a line begins with a &gt; character (or space followed by &gt;) it
is considered a quote. That line will be given the Quote1 Color (first
level quote). If there is a second level of quoting then the Quote2 Color
will be used. <EM>Alpine</EM> considers there to be a second level of quoting if
that first &gt; is followed by another &gt; (or space followed by &gt;).
If there are characters other than whitespace and &gt; signs, then it isn't
considered another level of quoting. Similarly, if there is a third level
of quoting the Quote3 Color will be used. If there are more levels after
that the Quote Colors are reused. If you define all three colors then it
would repeat like Color1, Color2, Color3, Color1, Color2, Color3, ...
If you only define the first two it would be Color1, Color2,
Color1, Color2, ...
If you define only the Quote1 Color, then the entire quote would be
that color regardless of the quoting levels.
By default, the Quote1 Color is black characters on a greenish-blue background;
the Quote2 Color is black characters on a dull yellow background; and
the Quote3 Color is black characters on a green background.
<P>

<DT> <A NAME="incoming-unseen-color"><EM>Incoming Unseen Color</EM></A>

<DD> If the option
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is turned on it is possible to highlight the folders that contain
unseen messages by coloring them with this color.
By default, this is the same as the Normal Color and no highlighting is done.
<P>
Usually the &quot;current&quot; folder (the folder the cursor is on)
is highlighted using reverse video.
If the current folder is colored because it contains unseen messages then
the color used to show that it is also the current folder is controlled
by the <A HREF="#cur-il-style"><EM>current-indexline-style</EM></A>
feature at the top of the SETUP COLOR screen.
<P>

<DT> <A NAME="signature-color"><EM>Signature Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for coloring the signature in the MESSAGE TEXT
screen. According to USENET conventions, the signature is defined as the
paragraph following the &quot;sigdashes&quot;, that is, the special line
consisting of the three characters
&quot;--&nbsp;&quot; (i.e., dash, dash, and space). <EM>Alpine</EM> allows for one
empty line right after the sigdashes to be considered as part of the
signature.
By default, the Signature Color is blue characters on a white background.
<P>

<DT> <A NAME="prompt-color"><EM>Prompt Color</EM></A>

<DD> The color <EM>Alpine</EM> uses for confirmation prompts and questions
which appear in the status message line near the bottom of the screen.
By default, the Prompt Color is the same as the Reverse Color.
<P>

</DL>

<H3><A NAME="index-colors"></A>Index Colors</H3>

You may add color to the single character symbols which give the status
of each message in the MESSAGE INDEX.
By default the characters &quot;+&quot;, &quot;*&quot;, &quot;D&quot;,
&quot;A&quot;, and &quot;N&quot; show up near the left hand side of the
screen, depending on whether the message is addressed to you, and whether
the message is marked Important, is Deleted, is Answered, or is New.
You may set the color of those symbols.
By default, all of these symbols are drawn with the same color as the rest
of the index line they are a part of.
<P>
Besides coloring the message status symbols, you may also color the
entire index line.
This is done by using the
<A HREF="#index-color-config">Index Line Color</A> configuration screen.
It is also possible to color
(<A HREF="#keywords">keywords</A>
in the index using the
Setup/Kolor screen (<A HREF="#keyword-colors">Keyword Colors</A>);
the <A HREF="#index-arrow-color">ARROW</A> cursor;
the Subject using
<A HREF="#index-subject-color">Index Subject Color</A>;
the From using
<A HREF="#index-from-color">Index From Color</A>;
and the
<A HREF="#index-opening-color">Index Opening</A> text.
<P>

<DL COMPACT>

<DT> <A NAME="index-to-me-color"><EM>Index-to-me Symbol Color</EM></A>

<DD> The color used for drawing the &quot;+&quot; symbol which signifies a
message is addressed directly to you.
<P>

<DT> <A NAME="index-important-color"><EM>Index-important Symbol Color</EM></A>

<DD> The color used for drawing the &quot;*&quot; symbol which signifies a
message has been flagged Important.
<P>

<DT> <A NAME="index-deleted-color"><EM>Index-deleted Symbol Color</EM></A>

<DD> The color used for drawing the &quot;D&quot; symbol which signifies a
message has been marked Deleted.
<P>

<DT> <A NAME="index-answered-color"><EM>Index-answered Symbol Color</EM></A>

<DD> The color used for drawing the &quot;A&quot; symbol which signifies a
message has been answered.
<P>

<DT> <A NAME="index-new-color"><EM>Index-new Symbol Color</EM></A>

<DD> The color used for drawing the &quot;N&quot; symbol which signifies a
message is New.
<P>

<DT> <A NAME="index-recent-color"><EM>Index-recent Symbol Color</EM></A>

<DD> The color used for drawing the &quot;R&quot; symbol which signifies a
message is Recent (only visible if the &quot;IMAPSTATUS&quot; or &quot;SHORTIMAPSTATUS&quot; token is
part of the
<A HREF="#index-format"><EM>index-format</EM></A> option).
<P>

<DT> <A NAME="index-unseen-color"><EM>Index-unseen Symbol Color</EM></A>

<DD> The color used for drawing the &quot;U&quot; symbol which signifies a
message is Unseen (only visible if the &quot;IMAPSTATUS&quot; or &quot;SHORTIMAPSTATUS&quot; token is
part of the
<A HREF="#index-format"><EM>Index-Format</EM></A> option).
<P>

<DT> <A NAME="index-pri-color"><EM>Index-priority Symbol Colors</EM></A>

<DD> The colors used for drawing the tokens &quot;PRIORITY&quot;,
 &quot;PRIORITYALPHA&quot;, and  &quot;PRIORITY!&quot; when these are
configured as part of the
<A HREF="#index-format"><EM>Index-Format</EM></A> option.
You may set the color used to draw these tokens by use of the colors
Index High Priority Symbol Color and Index Low Priority Symbol Color.
This coloring takes place for all but the current index line, and the Priority
Color appears to be in front of any color from an Index Color Rule.
If the priority has a value of 1 or 2 the High Priority color will be
used,
and if the value is 4 or 5 the Low Priority color will be used.
<P>
If you don't set these colors the index line will be colored in the same color as
the bulk of the index line.
<P>

<DT> <A NAME="index-arrow-color"><EM>Index-arrow Symbol Color</EM></A>

<DD> The color used for drawing the &quot;ARROW&quot; token when it is
configured as part of the
<A HREF="#index-format"><EM>Index-Format</EM></A> option.
<P>

<DT> <A NAME="index-subject-color"><EM>Index-subject Symbol Color</EM></A>

<DD> You may set the color used to draw the Subject part of the index line.
This coloring takes place for all but the current index line, and the Subject
Color appears to be in front of any color from an Index Color Rule.
<P>
If you don't set this color it will be colored in the same color as
the bulk of the index line.
<P>

<DT> <A NAME="index-from-color"><EM>Index-from Symbol Color</EM></A>

<DD> You may set the color used to draw the From part of the index line.
This coloring takes place for all but the current index line, and the From
Color appears to be in front of any color from an Index Color Rule.
<P>
If you don't set this color it will be colored in the same color as
the bulk of the index line.
<P>

<DT> <A NAME="index-opening-color"><EM>Index-opening Symbol Color</EM></A>

<DD> It is possible to configure the
<A HREF="#index-format"><EM>Index-Format</EM></A> option
so that it includes the subject followed by the &quot;opening&quot; text of the
message if there is enough space.
This is done by using one of the tokens SUBJECTTEXT, SUBJKEYTEXT, or
SUBJKEYINITTEXT.
The color used for drawing this opening text is given by this option.
The coloring happens for all but the current index line, and this opening
color appears to be in front of any color from an Index Color Rule.
<P>
By default the Index Opening Color is gray characters on a white background.
<P>

</DL>
<P>
The default colors for these symbols are:
<TABLE>
<TR> <TD> &nbsp;&nbsp;Index-to-me&nbsp;&nbsp;&nbsp;&nbsp; </TD> <TD> black on cyan </TD> </TR>
<TR> <TD> &nbsp;&nbsp;Index-important </TD> <TD> white on bright red </TD> </TR>
<TR> <TD> &nbsp;&nbsp;Index-deleted&nbsp;&nbsp; </TD> <TD> same as Normal Color </TD> </TR>
<TR> <TD> &nbsp;&nbsp;Index-answered&nbsp; </TD> <TD> bright red on yellow </TD> </TR>
<TR> <TD> &nbsp;&nbsp;Index-new&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </TD> <TD> white on magenta </TD> </TR>
<TR> <TD> &nbsp;&nbsp;Index-recent&nbsp;&nbsp;&nbsp; </TD> <TD> same as Normal Color </TD> </TR>
<TR> <TD> &nbsp;&nbsp;Index-unseen&nbsp;&nbsp;&nbsp; </TD> <TD> same as Normal Color </TD> </TR>
</TABLE>

<H3><A NAME="header-colors"></A>Header Colors</H3>

You may add color to the header fields in the MESSAGE TEXT screen.
The
<P>
<DL COMPACT>
<DT> <A NAME="header-general-color"><EM>Header-general Color</EM></A>

<DD> may be used to color all of the headers of
the message.
</DL>
<P>
It is also possible to set the colors for specific header fields,
for example for the Subject or From fields, using the
<A HREF="#viewer-hdr-colors"><EM>viewer-hdr-colors</EM></A>
option.
<P>
For Header Colors,
there is an additional line on the configuration
screen labeled &quot;Pattern to match&quot;.
If you leave that blank, then the whole field for that header will
always be colored.
However, if you give a pattern to match, the coloring will only take place
if there is a match for that pattern in the value of the field.
For example, if you are working on a color for the Subject header and
you fill in a pattern of &quot;important&quot;, then only Subjects which
contain the word &quot;important&quot; will be colored.
For address fields like From or To, a pattern match will cause only the
addresses which match the pattern to be colored.
<P>
If the pattern you enter is a comma-separated list of patterns, then coloring
happens if any of those patterns matches.
<P>

<H3><A NAME="keyword-colors"></A>Keyword Colors</H3>

Sets the colors <EM>Alpine</EM> uses for Keyword fields in the MESSAGE INDEX screen.
Keywords may be displayed as part of the Subject of a message by using
the &quot;SUBJKEY&quot; or &quot;SUBJKEYINIT&quot; tokens in the
<A HREF="#index-format">Index-Format</A> option.
Keywords may also be displayed in a column of their own in the MESSAGE INDEX
screen by using the &quot;KEY&quot; or &quot;KEYINIT&quot; tokens.
<P>
For example, you might have set up a Keyword
&quot;Work&quot; using the
<A HREF="#keywords">Keywords</A>
option in the Setup/Config screen.
You could cause that Keyword to show up as a special color
by setting up the Keyword Color using this option, and then including it
in the MESSAGE INDEX screen using one of the tokens listed above in the
Index-Format.
<P>

<H3><A NAME="index-line-colors"></A>Index Line Colors</H3>

You may color whole index lines by using roles.
This isn't configured in the Setup Colors screen, but is configured in
the <A HREF="#index-color-config">Setup Rules IndexColor</A> screen.

<H2><A NAME="index-color-config"></A>Index Line Color Configuration</H2>

Index Line Color causes lines in the MESSAGE INDEX screen to be colored.
This action is only available if your terminal is capable of displaying
color and color display has been enabled with the
<A HREF="#color-style"><EM>Color-Style</EM></A> option.
(In PC-Alpine, color is always enabled so there is no option to turn on.)
<P>
Each rule has a &quot;Pattern&quot;,
which is used to decide which of the rules is used; and the color which
is used if the Pattern matches a particular message.

<H3>Rule Patterns</H3>

In order to determine whether or not a message matches a rule the message is
compared with the rule's Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
&quot;<A HREF="#patterns-section">here</A>&quot;.

<H3>Index Line Color</H3>

This is the color that index lines are colored when there is a matching
Pattern.
This colors the whole index line, except possibly the status letters
which may be colored separately using
the <A HREF="#color-config">Setup Kolor</A> screen.

<H2><A NAME="role-config"></A>Role Configuration</H2>

You may play different roles depending on who you are replying to.
For example, if you are replying to a message addressed to <EM>help-desk</EM> you
may be acting as a Help Desk Worker.
That role may require that you use a different return address and/or
a different signature.
<P>
Roles are optional.
If you set up roles they work like this:  Each role has a set of
&quot;Uses&quot;, which indicate whether or not a role is eligible to be
considered for a particular use; a &quot;Pattern&quot;,
which is used to decide which of the eligible roles is used; and a set
of &quot;Actions&quot;, which are taken when that role is used.
When you reply to a message, the message you are replying to is compared
with the Patterns of the roles marked as eligible for use when replying.
The comparisons start with the first eligible role and keep going until there
is a match.
If a match is found, the matching role's Actions are taken.
<P>
It is also possible to set a default role and to change that role during
your <EM>Alpine</EM> session.
When you start <EM>Alpine</EM> no default role will be set.
You may set or change the current default role by using the &quot;D&quot;
command in the role selection screen.
You'll see that screen while composing a message and being asked to select
a role.
An easy way to get to that screen is to use the Role Command to
compose a message.
You may find a default role useful if you normally perform the duties of one
of your roles for a while, then you switch to another role and stay in the
new role for another period of time.
It may be easier than using the Role Command to select the role each time you
compose a message.

<H3>Role Uses</H3>

There are three types of use to be configured;
one for Replying, one for Forwarding, and one for Composing.
These indicate whether or not you want a role to be considered when you
type the Reply, Forward, or Compose commands.
(The Role command is an alternate form of the Compose command, and it is
not affected by these settings.)
Each of these Use types has three possible values.
The value &quot;Never&quot;
means that the role will never be considered as a candidate for use with
the corresponding command.
For example, if you set a role's Reply Use to Never, then when you Reply to
a message, the role won't even be considered.
(That isn't quite true. If the message you are replying to matches some other
role which requires confirmation,
then there will be a ^T command available which allows you to select a role
from all of your roles, not just the reply-eligible roles.)
<P>

The options &quot;With confirmation&quot; and &quot;Without confirmation&quot;
both mean that you do want to consider this role when using the corresponding
command.
For either of these settings the role's Pattern will
be checked to see if it matches the message.
For Reply Use, the message used to compare the Patterns with is the message
being replied to.
For Forward Use, the message used to compare the Pattern with is the message
being forwarded.
For Compose Use, there is no message, so the parts of the Pattern which depend
on a message (everything other than Current Folder Type) are ignored.
In all cases, the Current Folder is checked if defined.
If there is a match then this role will either be used without confirmation
or will be the default when confirmation is asked for, depending on
which of the two options is selected.
If confirmation is requested, you will have a chance to
choose No Role instead of the offered role, or to
change the role to any one of your other roles (with the ^T command).

<H3>Role Patterns</H3>

In order to determine whether or not a message matches a role the message is
compared with the Role Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
&quot;<A HREF="#patterns-section">here</A>&quot;.
<P>
Since header patterns, AllText patterns, and BodyText patterns which are unset are ignored,
a role which has all header patterns unset, the AllText pattern unset,
the BodyText pattern unset,
the Score Interval unset, and the Current Folder Type set to
&quot;Any&quot; may be used as a default role.
It should be put last in the list of roles since the matching
starts at the beginning and proceeds until one of the roles is a match.
If no roles at all match, then <EM>Alpine</EM> will
use its regular methods of defining the role.
If you wanted to, you could define a different &quot;default&quot; role
for Replying, Forwarding, and Composing by setting the
&quot;Use&quot; fields appropriately.

<H3>Role Actions</H3>

Once a role match is found, the role's Actions are taken.
For each role there are several possible actions that may be defined.
They are actions to set the From address, the Reply-To address,
the Fcc, the Signature file, and the Template file.

<H4>Initialize Settings Using Role</H4>

This is a power user feature.
You will usually want to leave this field empty.
The value of this field is the nickname of another one of your roles.
The Action values from that other role
are used as the initial values of the Action items for this role.
If you put something in any of the action fields for this role, that will
override whatever was in the corresponding field of the initializer role.
<P>
You might use this field if the &quot;Action&quot; part of one of your roles
is something you want to use in more than one role.
Instead of filling in those action values again for each role, you
may give the nickname of the role where the values are filled in.
It's just a shortcut way to define Role Actions.
<P>
Here's an example to help explain how this works.
Suppose you have a role with nickname &quot;role1&quot; and role1 has
(among other things)
<P>
<CENTER><SAMP>Set Reply-To = The Pres &lt;president@example.com&gt;</SAMP></CENTER>
<P>
set.
If in &quot;role2&quot; you set &quot;Initialize settings using role&quot; to
&quot;role1&quot;, then role2 will inherit the Set Reply-To value
from role1 by default (and any of the other inheritable action values
that are set).
So if role2 had
<P>
<CENTER><SAMP>Set Reply-To = &lt;No Value Set&gt;</SAMP></CENTER>
<P>
defined, the Reply-To used with role2 would be &quot;The Pres &lt;president@example.com&gt;&quot;
However, if role2 had
<P>
<CENTER><SAMP>Set Reply-To = VP &lt;vicepresident@example.com&gt;</SAMP></CENTER>
<P>
defined, then the Reply-To used with role2 would be &quot;VP &lt;vicepresident@example.com&gt;&quot; instead.
<P>
If you wish,
you may choose a nickname from your list of roles by using the
&quot;T&quot; command.
If the role you are using to initialize also has a role it initializes from,
then that initialization happens first.
That is, inheritance works as expected with the grandparent and
great-grandparent (and so on) roles having the expected effect.

<H4>Set From</H4>

This field consists of a single address which will be used as the From
address on the message you are sending.
This should be a fully-qualified address like
<P>
<CENTER><SAMP>Full Name &lt;user@domain&gt;</SAMP></CENTER>
<P>
or just
<P>
<CENTER><SAMP>user@domain</SAMP></CENTER>
<P>
If this is left blank, then the normal From address will be used.

<H4>Set Reply-To</H4>

The Reply-To address is the address used on the Reply-To line of the message
you are sending.
You don't need a Reply-To address unless it is different from the From address.
This should be a fully-qualified address like
<P>
<CENTER><SAMP>Full Name &lt;user@domain&gt;</SAMP></CENTER>
<P>
or just
<P>
<CENTER><SAMP>user@domain</SAMP></CENTER>
<P>
If this is left blank, then there won't be a Reply-To address unless
you have configured one specially with the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A>
configuration option.

<H4>Set Other-Hdrs</H4>

This field gives you a way to set values for headers besides
&quot;From&quot; and &quot;Reply-To&quot;.
If you want to set either of those, use the specific
&quot;Set From&quot; and &quot;Set Reply-To&quot; settings.
<P>
This field is similar to the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> option.
Each header you specify here must include the header tag 
(&quot;To:&quot;, &quot;Approved:&quot;, etc.)
and may optionally include a value for that header.
In order to see these headers when you compose using this role you 
must use the rich header command.
Here's an example which shows how you might set the To address.
<P>
<CENTER><SAMP>Set Other Hdrs = To: Full Name &lt;user@domain&gt;</SAMP></CENTER>
<P>
Headers set in this way are different from headers set with the
customized-hdrs option in that the value you give for a header here
will replace any value that already exists.
For example, if you are Replying to a message there will already be at
least one address in the To header (the address you are Replying to).
However, if you Reply using a role which sets the To header, that role's
To header value will be used instead.
The customized-hdrs headers are defaults.
<P>
Limitation: Because commas are used to separate the list of
Other Headers, it is not possible to have the value of a
header contain a comma;
nor is there currently an &quot;escape&quot; mechanism provided
to make this work.

<H4>Set Fcc</H4>

This field consists of a single folder name which will be used in
the Fcc field of the message you are sending.
You may put anything here that you would normally type into the Fcc
field from the composer.
<P>
In addition, an fcc of &quot;&quot; (two double quotation marks) means
no Fcc.
<P>
A blank field here means that <EM>Alpine</EM> will use its normal rules for deciding
the default value of the Fcc field.
For many roles, perhaps most, it may make more sense for you to use the
other <EM>Alpine</EM> facilities for setting the Fcc.
In particular, if you want the Fcc to depend on who you are sending the
message to then the <A HREF="#fcc-name-rule"><EM>fcc-name-rule</EM></A>
is probably more useful.
In that case, you would want to leave the Fcc field here blank.
However, if you have a role that depends on who the message you are replying
to was From, or what address that message was sent to;
then it might make sense to set the Fcc for that role here.

<H4>Set LiteralSig</H4>

This field contains the actual text for your signature, as opposed to
the name of a file containing your signature.
If this is defined it takes precedence over any value set in the
<EM>Set Signature</EM> field.
<P>
This is simply a different way to store the signature.
The signature is stored inside your Alpine configuration file instead of in
a separate signature file.
Tokens work the same way they do with <EM>Set Signature</EM>.
<P>

The two character sequence &#92;n (backslash followed by
the character n) will be used to signify a line-break in your signature.
You don't have to enter the &#92;n, but it will be visible in the
CHANGE THIS ROLE RULE window after you are done editing the signature.

<H4>Set Signature</H4>

The Signature is the name of a file to be used as the signature file when
this role is being used.
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>,
but the rest of the processing works as if the contents came from a file.

<P>
Signature files may be stored remotely on an IMAP server.
In order to do that you just give the file a remote name.
This works just like the regular
<A HREF="#sig-file">signature-file</A>
option which is configured from the Setup/Configuration screen.
A remote signature file name might look like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
<P>
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/sig3</SAMP></CENTER>
<P>
Once you have named the remote signature file you create its
contents by using the &quot;F&quot; &quot;editFile&quot; command when the
cursor is on the &quot;Set Signature&quot;
line of the role editor.

<P>
Besides containing regular text, a signature file may also
contain (or a signature program may produce) tokens which are replaced with text
which depends on the message you are replying to or forwarding.
The tokens all look like _word_ (a word surrounded by underscores).
For example, if the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
is included in the text of the signature file, then when you reply to
or forward a message, the token will be replaced with the actual date
the message you are replying to or forwarding was sent.
<P>
If you use a role which has a signature file for a plain composition
(that is, not a reply or forward) then there is no original message, so
any tokens which depend on the message will be replaced with nothing.
So if you want a signature file to be useful for new compositions it
shouldn't include any of the tokens which depend on the message being
replied to or forwarded.
<P>
The list of available tokens is
<A HREF="#index-tokens">here</A>.
<P>
Actually, for the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="#reply-token-conditionals">here</A>.
<P>
In the very unlikely event that you want to include a literal token in
a signature file, you must precede it with a backslash character.
For example, to include the literal text _DATE_ you must actually use
&#92;_DATE_.
It is not possible to have a literal backslash followed by an expanded token.
<P>
A blank field here means that <EM>Alpine</EM> will use its normal rules for deciding
which file (if any) to use for the signature file.

<H4>Set Template</H4>

A Template is the name of a file to be included in the message when this
role is being used.
The template file is a file which is included at the top of the message you
are composing.
<P>
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>,
but the rest of the processing works as if the contents came from a file.
<P>
Template files may be stored remotely on an IMAP server.
In order to do that you just give the file a remote name.
This works just like the regular
<A HREF="#sig-file">signature-file</A>
option which is configured from the Setup/Configuration screen.
A remote template file name might look like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER>
<P>
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/templ3</SAMP></CENTER>
<P>
Once you have named the remote template file you create its
contents by using the &quot;F&quot; &quot;editFile&quot; command when the
cursor is on the &quot;Set Template&quot;
line of the role editor.
<P>
Besides containing regular text, a template file may also
contain (or a template file program may produce) tokens which are replaced with text
which depends on the message you are replying to or forwarding.
The tokens all look like _word_ (a word surrounded by underscores).
For example, if the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
is included in the text of the template file, then when you reply to
or forward a message, the token will be replaced with the actual date
the message you are replying to or forwarding was sent.
<P>
If you use a role which has a template file for a plain composition
(that is, not a reply or forward) then there is no original message, so
any tokens which depend on the message will be replaced with nothing.
So if you want a template file to be useful for new compositions it
shouldn't include any of the tokens which depend on the message being
replied to or forwarded.
<P>
The list of available tokens is
<A HREF="#index-tokens">here</A>.
<P>
Actually, for the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="#reply-token-conditionals">here</A>.
<P>
In the very unlikely event that you want to include a literal token in
a template file, you must precede it with a backslash character.
For example, to include the literal text _DATE_ you must actually use
&#92;_DATE_.
It is not possible to have a literal backslash followed by an expanded token.
<P>
A blank field here means that <EM>Alpine</EM> will not use a template file when
this role is being used.

<H4>Use SMTP Server</H4>

If this field has a value, then it will be used as the SMTP server
to send mail when this role is being used (unless the SMTP server variable
is set in the system-wide fixed configuration file).
It has the same semantics as the
<A HREF="#smtp-server"><EM>smtp-server</EM></A>
variable in the Setup/Config screen.
When you postpone the composition this SMTP server list will be saved
with the postponed composition and it cannot be changed later.
Because of that, you may want to make this a list of SMTP servers
with the preferred server at the front of the list and alternate servers
later in the list.

<P>
If any of the actions are left unset, then the action depends on what
is present in the &quot;Initialize settings using role&quot; field.
If you've listed the nickname of another one of your roles there, then the
corresponding action from that role will be used here.
If that action is also blank, or if there is no nickname specified,
then <EM>Alpine</EM> will do whatever it normally does to set these actions.
This depends on other configuration options and features you've set.

<H2><A NAME="filter-config"></A>Filtering Configuration</H2>

The software which actually delivers mail (the stuff that happens
before <EM>Alpine</EM> is involved) for you is in a better position to do mail filtering
than <EM>Alpine</EM> itself.
If possible, you may want to look into using that sort of mail filtering to
deliver mail to different folders, delete it, or forward it.
However, if you'd like <EM>Alpine</EM> to help with this, <EM>Alpine</EM>'s filtering is for you.
<P>
Filtering is a way to automatically move certain messages from one folder
to another or to delete messages.
It can also be used to set message status bits (Important, Deleted, New,
Answered).
<EM>Alpine</EM> doesn't have the ability to forward mail to another address.
<P>
Each filtering rule has a &quot;Pattern&quot; and a &quot;Filter Action&quot;.
When a folder is opened, when new mail arrives in an open folder, or
when mail is Expunged from a folder; each
message is compared with the Patterns of your filtering rules.
The comparisons start with the first rule and keep going until there
is a match.
If a match is found, the message may be deleted or moved, depending on
the setting of the Filter Action.
If the message is not deleted, it may have its status altered.
<P>
For efficiency, each message is usually only checked once.
When new mail arrives, the new messages are checked but not the old.
There are some exceptions to this rule.
The expunge command will cause all messages to be rechecked, as will
editing of the filtering rules.

<P>
<EM>NOTE:</EM>
When setting up a Pattern used to delete messages,
it is recommended that you test the Pattern first with a &quot;Move&quot;
folder specified in
case unintended matches occur.  Messages that are deleted will be removed 
from the folder and <EM>unrecoverable</EM> from within <EM>Alpine</EM> after the
next Expunge command or once the folder being filtered has been closed.

<H3>Filter Patterns</H3>

In order to determine whether or not a message matches a filter the message is
compared with the Filter's Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
&quot;<A HREF="#patterns-section">here</A>&quot;.
<P>
Since filtering is a potentially destructive action, if you have a filtering
Pattern with nothing other than Current Folder Type set, that filtering
rule is ignored.

<H3>Filter Actions</H3>

Once a filter match is found for a particular message, there are some actions
which may be taken.
First, the message may have its status changed.
This is the same message status that you can manipulate manually using the
Flag Command.
There are four elements of message status that you can control.
You can set or clear the Important status, the New status, the Deleted
status, and the Answered status.
Of course, if the filter is going to delete the message,
then there is no point in setting message status.
You may also set or clear user-defined
<A HREF="#keywords">keywords</A> for a message.
<P>
Second, the filter may delete or move the message.
Deleting the message marks it Deleted and removes it from view.
It is effectively gone forever (though it technically is still there until
the next expunge command, which may happen implicitly).
Moving the message moves it from the open folder into the folder
listed on the &quot;Folder List&quot; line of the filter configuration.
If you list more than one folder name (separated by commas) then the message
will be copied to each of those folders.
In any case, if &quot;Delete&quot; or &quot;Move&quot; is set then the
message is removed from the current folder.
If you just want to set the messages status without deleting it from
the folder, then set the filter action to
&quot;Just Set Message Status&quot;.
<P>
(There is no way to do a Copy instead of a Move, due to the difficulties
involved in keeping track of whether or not a message has
already been copied by a previous <EM>Alpine</EM> session.)

<H4><A NAME="move-only-if-not-deleted"></A>Move-only-if-not-deleted option</H4>

If you have specified a Move to Folder to filter messages into, then this
option has an effect.
If this option is set then messages will only be moved into the specified folder
if they aren't already marked deleted.
This might be useful if you have more than one <EM>Alpine</EM> session running
simultaneously and you don't want messages to be filtered into a folder
more than once.
This method is not foolproof.
There may be cases where a message gets marked deleted and so it is never
filtered into the folder.
For example, if you deleted it in another <EM>Alpine</EM> or
another mail program that didn't know about the filtering rule.
<P>
This option has no effect if the Filter Action is not set to Move.

<H4><A NAME="dont-quit-even-if-rule-matches"></A>Dont-quit-even-if-rule-matches option</H4>

If this option is set then this is a non-terminating rule.
Usually, for each message, <EM>Alpine</EM> searches through the filter rules until
a match is found and then it performs the action associated with that rule.
Rules following the match are not considered.
If this option is set then the search for matches will continue at the next
rule.
<P>
If a non-terminating rule matches then the actions associated with
that rule, except for any implied deletion of the message, are performed
before the match for the next rule is checked.
For example, if the non-terminating rule sets the Important status, then that
status will be set when the next rule is considered.
However, if the non-terminating rule Moves the message, the message will
actually be copied instead of copied and deleted so that it is still there
for the next rule.
A moved message is deleted after all the relevant rules have been checked.
The name of the &quot;Move&quot; action is confusing in this case because
a single message can be moved to more than one folder.
It turns the Move into a Copy instead, but it is still followed by a deletion
at the end.
<P>
This option may be useful if you want to have a single message filtered to
two different folders because it matches two different Patterns.
For example, suppose you normally filter messages to a particular mailing
list into one folder, and messages addressed directly to you into a second
folder.
If a message is sent to both you and the list (and you can tell that by
looking at the headers of the message) this option may give you a convenient
way to capture a copy to each folder.
(It may also cause you to capture two copies to each folder,
depending on whether your mail system delivers one or two copies of the
message to you and on how the list works.)

<H2><A NAME="scoring-config"></A>Scoring Configuration</H2>

Most people will not use scores at all, but if you do use them, here's how
they work in Alpine.
Using this screen, you may define Scoring rules.
The score for a message is calculated by looking at every Score rule defined
and adding up the Score Values for the ones which match the message.
If there are no matches for a message, it has a score of zero.
Message scores may be used a couple of ways in Alpine.

<H3>Sorting by Score</H3>

One of the methods you may use to sort message indexes is to sort by
score.
The scores of all the messages in a folder will be calculated and then
the index will be ordered by placing the messages in order of ascending or
descending score.

<H3>Scores for use in Patterns</H3>

The Patterns used for Roles, Index Line Coloring, and Filtering have a
category labeled &quot;Score Interval&quot;.
When a message is being compared with a Pattern to check for a match, if
the Score Interval is set only messages which have a score somewhere in
the interval are a match.

<H3>Scoring Rule Patterns</H3>

In order to determine whether or not a message matches a scoring rule
the message is compared with the rule's Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
&quot;<A HREF="#patterns-section">here</A>&quot;.

<P>
Actually, Scoring rule Patterns are slightly different from the other types of
Patterns because Scoring rule Patterns don't contain a Score Interval.
In other words, when calculating the score for a message, which is done
by looking at the Scoring rule Patterns, scores aren't used.

<H3>Score Value</H3>

This is the value that will be added to the score for a message if the
rule's Pattern is a match.
Each individual Score Value is an integer between -100 and 100, and the
values from matching rules are added together to get a message's score.
There is also a way to extract the value from a particular header of each
message. See the help text for Score Value for further information.

<H2><A NAME="other-config"></A>Other Rules Configuration</H2>

Using this screen, you may define configuration Rules which don't fit
nicely into the other Rules categories.

<H3>Other Rule Patterns</H3>

Other Rules are a little different from the rest of the Rules because
they depend only on the current folder, and not on a particular message.
In order to determine whether or not a rule's actions should be applied
the current folder is compared with the rule's Pattern, which consists
of only the Current Folder Type.
Current Folder Type works the same for Other Rules as it does for Roles,
Filtering, Index Coloring, and Scoring.
Keep in mind that the only part of the Pattern which applies to Other
Rules is the Current Folder Type when looking at the description of
Patterns given
&quot;<A HREF="#patterns-section">here</A>&quot;.

<H3>Other Rule Actions</H3>

Once a pattern match is found, the rule's Actions are taken.
Neither of the following two rule's depends on a message for its match.
That means that all the parts of the Pattern which depend on matching an
attribute of a message are ignored.
So the only part of the Pattern that matters for these Actions is
the Current Folder Type.

<H4>Set Sort Order</H3>

When you enter a new folder, these rules will be checked to see if you
have set a sort order which is different from your default sort order.
The default is set in the Setup/Config screen with
the <A HREF="#sort-key">Sort-Key</A> option.
If the Sort Order action is set, then the folder will be displayed sorted in
that sort order instead of in the default order.
<P>
A possible point of confusion arises when you change the configuration
of the Sort Order for the currently open folder.
The folder will normally be re-sorted when you go back to viewing the
index.
However, if you have manually sorted the folder with the
Sort command, it will not be re-sorted.

<H4>Set Index Format</H3>

When you enter a new folder, these rules will be checked to see if you
have set an Index Format which is different from your default Index Format,
which is set with the
<A HREF="#index-format"><EM>Index-Format</EM></A> option.
If so, the index will be displayed with this format instead of the default.

<H4>Set Startup Rule</H4>

When you enter a new folder, these rules will be checked to see if you
have set a startup rule which is different from the default startup rule.
The default for incoming folders is set in the Setup/Config screen with
the &quot;incoming-startup-rule&quot; option.
The default for folders other than INBOX that are not part of your
incoming collection
(see <A HREF="#enable-incoming-folders">enable-incoming-folders</A> feature)
is to start with the last message in the folder.
If the Startup Rule is set to something other than &quot;default&quot;,
then the rule will determine which message will be the current message when
the folder is first opened.
<P>
The various startup rule possibilities work the same here as they do in
the incoming collection, except that the folder can be any specific
folder or any folder type.

<H2><A NAME="search-rules-config"></A>Search Rules Configuration</H2>

One of the commands that becomes available when that feature is turned on
is the &quot;; Select&quot; command, which is used in the MESSAGE INDEX
screen to select a set of messages.
One way of selecting messages is to use a Rule.
All of the messages which match (or don't match if you wish)
a Rule's Pattern will be selected.
<P>
Any of your Rules may be used for this purpose.
You might already have Rules set up for filtering, index line color, scores, or roles;
and you may use any of those Rules with the Select command.
However, you might find it more convenient to set up a separate set of Rules
just for this purpose without having to worry about what other effects
they may cause.
That is the purpose of these Select Rules.

<H3>Rule Patterns</H3>

In order to determine whether or not a message is selected by a rule the
message is 
compared with the rule's Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
&quot;<A HREF="#patterns-section">here</A>&quot;.
<P>
There is no action associated with these Search Rules.
Only their Patterns are used.

<H2><A NAME="patterns-section"></A>Patterns</H2>

Patterns are used with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules.
Patterns are compared with a message to see if there is a match.
For Filtering, the messages being checked are all the messages in the
folder, one at a time.
For Index Line Coloring, each message that is visible on the screen is
checked for matches with the Index Coloring Patterns.
Roles are used with the Reply, Forward, and Compose commands.
For Reply, the message used to compare the Pattern with is the message
being replied to;
for Forward, the message used to compare the Pattern with is the message
being forwarded;
and for Compose, there is no message, so the parts of the Pattern which depend
on a message (everything other than Current Folder Type and the
Beginning of Month and Year)
are not used.
Only the Current Folder Type matters for Compose (plus the Beginning of
Month or Year, which you wouldn't usually use for a Role).
For Scoring, the message being scored is compared with all of the Score
Patterns, and the Score Values from the ones that match are added together to 
get the message's score.
For Other Rules, there is no message. Only the Current Folder Type is checked
for Other Rules.
<P>
Each Pattern has several possible parts, all of which are optional.
In order for there to be a match, <EM>ALL</EM> of the
<EM>defined</EM> parts of the Pattern must match the message.
If a part is not defined it is considered a match.
For example, if the To pattern is not defined it will be
displayed as
<P>
<CENTER>To pattern = &lt;No Value Set&gt;</CENTER>
<P>
That is considered a match because it is not defined.
This means that the Pattern with nothing defined is a match if the
Current Folder Type matches, but there is an exception.
Because filtering is a potentially destructive action, filtering Patterns
with nothing other than Current Folder Type defined are ignored.
If you really want a filtering Pattern to match all messages (subject to
Current Folder Type) the best way to do it is to define a Score interval
which includes all possible scores.
This would be the score interval <SAMP>(-INF,INF)</SAMP>.
This can be used even if you haven't defined any rules to Set Scores.
<P>
There are six predefined header patterns called the To, From, Sender, Cc, News,
and Subject patterns.
Besides those six predefined header patterns, you may add
additional header patterns with header fieldnames of your choosing.
You add an extra header pattern by placing the cursor on one of the
patterns while in the role editor and using the &quot;eXtraHdr&quot; command.
The Recip pattern is a header pattern which stands for Recipient (To OR Cc)
and the Partic pattern is a header pattern which stands for
Participant (From OR To OR Cc).
(Defining the Recip pattern does not have the same effect as defining both
the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.)
Similar to the header patterns are the AllText pattern and the BodyText pattern.
Instead of comparing this pattern's text against only the contents of
a particular header field, the text for the AllText pattern is compared
with text anywhere in the message's header or body, and the text for the
BodyText pattern is compared with text anywhere in the message's body.
<P>
Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the
&quot;!&quot; &quot;toggle NOT&quot; command.
You can tell that <EM>NOT</EM> has been turned on by looking for the character
&quot;!&quot; at the beginning of the pattern line.
When the &quot;!&quot; is present, it reverses the meaning of the match.
That is, if the pattern matches then it is considered to NOT be a match, and
if it does not match it is considered to be a match.
<P>
Don't make the mistake of putting the &quot;!&quot; in the data field for
a pattern.
For example, if you type the characters &quot;!urgent&quot; into the Subject
pattern, the pattern will look like:
<P>
<PRE>
 Subject pattern = !urgent
</PRE>
<P>
This means you want to match the 7 character sequence &quot;!urgent&quot;.
In order to match messages which do not have &quot;urgent&quot; in
their Subject field, first type the characters &quot;urgent&quot; followed
by carriage return for the value of the Subject pattern, then negate it
by typing the &quot;!&quot; command.
It should look like
<P>
<PRE>
 ! Subject pattern = urgent
</PRE>
<P>
The contents of each of these header patterns (or the AllText or BodyText patterns) may
be a complete email address, part of an address, or a random set of
characters to match against.
It may also be a list of such patterns, which means you
are looking for a match against the first pattern in the list <EM>OR</EM>
the second pattern <EM>OR</EM> the third and so on.
For example, a Subject pattern equal to
<P>
<PRE>
 Subject pattern = urgent
                   emergency
                   alert
</PRE>
<P>
would match all messages with a subject which contained at least one
of those words.
It would also match subjects containing the words &quot;alerts&quot; or
&quot;Urgently&quot;.
<P>
The same example with &quot;NOT&quot; turned on would be
<P>
<PRE>
 ! Subject pattern = urgent
                     emergency
                     alert
</PRE>
<P>
which would match all messages with a subject which did NOT contain any of
those words.
You can use the &quot;Add Value&quot; command to add new words to the list,
or you can enter them as a comma-separated list.
<P>
(It is not possible to specify two patterns which must <EM>BOTH</EM> be
present for a match.
It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM>
pattern2 must be present,
and that is exactly what using a list does.)
<P>
The &quot;Current Folder Type&quot; and the &quot;Score Interval&quot; are
also part of the Pattern, although the &quot;Score Interval&quot; is not used
when checking for matches for Scoring.
There are five similar settings which relate to the status of the message.
These settings rely on the message being New or not, Deleted or not,
Answered or not, Important or not, and Recent or not.
There are also some other miscellaneous settings.
The first is the Age of the message in days.
Another is the Size of the message in bytes.
The third is a setting which detects whether or not the Subject of a
message contains raw 8-bit characters (unencoded characters with the most
significant bit set).
There is a setting which detects whether or not this is the first time
<EM>Alpine</EM> has been run this month (doesn't depend on individual messages),
and another which detects whether or not this is the first time <EM>Alpine</EM> has
been run this year.
Other parts of the Pattern detect whether or not the From address of a
message appears in your address book, whether or not certain keywords
are set for a message, and whether or not certain character sets are
used in a message.

<H3>Parts of a Pattern</H3>

<H4>Header patterns</H4>

A header pattern is simply text which is searched for in the corresponding
header field.
For example, if a Pattern has a From header pattern with the value
&quot;@company.com&quot;, then only messages which have a From header
which contains the text &quot;@company.com&quot; will be possible
matches.
Matches don't have to be exact.
For example, if the relevant field of a message contains the text
&quot;mailbox@domain&quot; somewhere
in it, then header patterns of &quot;box&quot;, or &quot;x@d&quot;, or
&quot;mailbox@domain&quot; are all matches.
<P>
All parts of the Pattern must match so, for example,
if a message matches a defined
From pattern, it still must be checked against the other parts of the
Pattern which have been defined.
The To header pattern is a slightly special case.
If the message being checked has a Resent-To header
and the feature <A HREF="#use-resent-to-in-rules">Use-Resent-To-in-Rules</A> is turned on, the addresses
there are used in place of the addresses in the To header.
This is only true for the To header.
Resent-cc and Resent-From headers are never used unless you add them
with the eXtraHdrs command.
<P>
The meaning of a header pattern may be negated with the
&quot;!&quot; &quot;toggle NOT&quot; command.
You can tell that <EM>NOT</EM> has been turned on by looking for the character
&quot;!&quot; at the beginning of the pattern line.
It would look something like
<P>
<PRE>
 ! From pattern = susan@example.com
</PRE>
<P>
When the &quot;!&quot; is present, it reverses the meaning of the match.
<P>
If you want to check for the presence of a header field but don't care
about its value, then
the empty pattern which you get by entering a pair of
double quotes (&quot;&quot;) should match any message which
has the corresponding header field.

<H4><A NAME="pattern_alltext">AllText patterns</A></H4>

AllText patterns are just like header patterns except that the text is
searched for anywhere in the message's headers or body, not just in the
contents of a particular header field.
<P>

<H4><A NAME="pattern_bodytext">BodyText patterns</A></H3>

BodyText patterns are just like header patterns except that the text is
searched for anywhere in the message's body, not just in the
contents of a particular header field.
<P>

If there is more than one header pattern or AllText pattern or BodyText pattern
for which you want to take the
same action there is a shorthand notation which may be used.
Any of these patterns may be a list of patterns instead of
just a single pattern.
If any one of the patterns in the list matches the message
then it is considered a match.
For example, if &quot;company1&quot; and &quot;company2&quot; both required
you to use the same role when replying to messages, you might have
a To pattern which looks like
<P>
<PRE>
 To pattern = company1.com
              company2.com
</PRE>
<P>
This means that if the mail you are replying to was addressed to
either &quot;anything@company1.com&quot; or &quot;anything@company2.com&quot;,
then this Pattern is a match and the same actions will be taken.
<P>
The meaning of an AllText or BodyText pattern may be negated with the
&quot;!&quot; &quot;toggle NOT&quot; command.
You can tell that <EM>NOT</EM> has been turned on by looking for the character
&quot;!&quot; at the beginning of the pattern line.
When the &quot;!&quot; is present, it reverses the meaning of the match.
<P>
A technicality: Since comma is the character used to separate multiple values
in any of the fields which may have multiple values (such as header patterns,
AllText patterns, BodyText patterns, keywords, folder lists, and so on),
you must escape comma with a
backslash (&#92;) if you want to include a literal comma in one of those fields.
In other words, if you type a backslash followed by a comma it will
be interpreted as a comma by <EM>Alpine</EM>, instead of as a separator between
pattern values.
All other backslashes (those not followed by a comma) are literal
backslashes and should not be escaped.
It's unlikely you'll ever need to enter a literal comma or backslash in
any of the patterns.

<H4>Current Folder Type</H4>

The &quot;Current Folder Type&quot; may be set to one of four different
values: &quot;Any&quot;, &quot;News&quot;, &quot;Email&quot;, or
&quot;Specific&quot;.
If the value is set to &quot;News&quot;, then the
Pattern will only match if the currently open folder is a newsgroup.
The value &quot;Email&quot; only matches if the current folder is not news and
the value &quot;Any&quot; causes any folder to match.
If the value of &quot;Current Folder Type&quot; is set to &quot;Specific&quot;,
then you must fill in a value for &quot;Folder&quot;, which is on the line
below the &quot;Specific&quot; line.
In this case you will only get a match if the currently open folder is
the specific folder you list.
You may give a list of folders instead of just a single
folder name, in which case the Pattern will match if the open folder is
any one of the folders in the list.
The name of each folder in the list may be either &quot;INBOX&quot;,
the technical specification
of the folder (like what appears in your configuration file) or, if the
folder is one of your incoming folders, it may be the nickname you've given
the folder.
Here are some samples of specific folder names:
<P>
<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
<P>
<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
<P>
<CENTER><SAMP>mail/local-folder</SAMP></CENTER>
<P>
The easiest way to fill in the &quot;Folder&quot; field is to use
the &quot;T&quot; command which is available when the &quot;Folder&quot; line is
highlighted, or to use the &quot;Take&quot; command with the configuration
feature
<A HREF="#enable-rules-under-take">&quot;enable-rules-under-take&quot;</A>
turned on.
<P>
When reading a newsgroup, there may be a performance penalty
incurred when collecting the information necessary to check whether
or not a Pattern matches a message.
For this reason, the default Current Folder Type is set to &quot;Email&quot;.
If you have Patterns with a Current Folder Type of either
&quot;Any&quot; or &quot;News&quot; and those Patterns are used for
Index Line Coloring or Scoring, you may experience
slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup.

<H4>Age Interval</H4>

The &quot;Age Interval&quot; may be set to an interval of message
ages which should be considered a match.
Like the other parts of the Pattern, if it is unset it will be ignored.
The Age Interval looks like
<P>
<CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
<P>
where &quot;min_age&quot; and &quot;max_age&quot; are integers greater
than or equal to zero.
The special value &quot;INF&quot; may be used for
the max value. It represents infinity.
<P>
Actually, this option may be defined as a list of intervals instead
of just a single interval.
The list is separated by commas.
It can look like
<P>
<CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
<P>
When there is an Age Interval defined, it is a match if the age, in days, of
the message is contained in any of the intervals.
The intervals include both endpoints.
<P>
Even though this option is called Age, it isn't actually
the <EM>age</EM> of the message.
Instead, it is how many days ago the message arrived in one of your folders.
If the current time is a little past midnight, then a message that arrived
just before midnight arrived yesterday, even though the message is only
a few minutes old.
By default, the date being used is not the date in the Date
header of the message.
It is the date that the message arrived in one of your folders.
When you Save a message from one folder to another that arrival date
is preserved.
If you would like to use the date in the Date header that is possible.
Turn on the option
<EM>use-date-header-for-age</EM>
near the bottom of the rule definition.
<P>
A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.

<H4><A NAME="pattern_size_interval">Size Interval</A></H3>

The &quot;Size Interval&quot; may be set to an interval of message
sizes which should be considered a match.
Like the other parts of the Pattern, if it is unset it will be ignored.
The Size Interval looks like
<P>
<CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
<P>
where &quot;min_size&quot; and &quot;max_size&quot; are integers greater
than or equal to zero.
The special value &quot;INF&quot; may be used for
the max value. It represents infinity.
<P>
Actually, this option may be defined as a list of intervals instead
of just a single interval.
The list is separated by commas.
It can look like
<P>
<CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
<P>
When there is a Size Interval defined, it is a match if the size, in bytes, of
the message is contained in any of the intervals.
The intervals include both endpoints.

<H4>Score Interval</H4>

The &quot;Score Interval&quot; may be set to an interval of message
scores which should be considered a match.
Like the other parts of the Pattern, if it is unset it will be ignored.
The Score Interval looks like
<P>
<CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
<P>
where &quot;min_score&quot; and &quot;max_score&quot; are integers between
-32000 and 32000.
The special values &quot;-INF&quot; and &quot;INF&quot; may be used for
the min and max values to represent negative and positive infinity.
<P>
Actually, a list of intervals may be used if you wish.
A list would look like
<P>
<CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
<P>
When there is a Score Interval defined, it is a match if the score for
the message is contained in any of the intervals in the list.
The intervals include the endpoints.
The score for a message is calculated by looking at every Score rule defined and
adding up the Score Values for the ones which match the message.
When deciding whether or not a Pattern matches a message for purposes of
calculating the score, the Score Interval is ignored.

<H4>Message Status</H4>

There are five separate message status settings.
By default, all five are set to the value &quot;Don't care&quot;, which
will match any message.
The value &quot;Yes&quot; means that the particular status must be true
for a match, and the value &quot;No&quot; means that the particular
status must not be true for a match.
For example, one of the five Message Status settings is whether a message
is marked Important or not.
A &quot;Yes&quot; means that the message must be Important to be
considered a match and &quot;No&quot; means that the message must not be
Important to be considered a match.
The same is true of the other four message status settings which depend
on whether or not the message is New; whether the message has 
been Answered or not; whether the message has been Deleted or not, and
whether the message is Recent or not. 
<P>
The nomenclature for New and Recent is a bit confusing:
<P>
New means that the message is Unseen.
It could have been in your mailbox for a long time but if you haven't looked
at it, it is still considered New.
That matches the default <EM>Alpine</EM> index display that shows an N for such a
message.
<P>
Recent means that the message was added to this folder since the last time
you opened the folder.
<EM>Alpine</EM> also shows an N by default for these types of messages.
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after
the other, a message would only show up as Recent in (at most) the first
<EM>Alpine</EM> session.

<H4>Message Keywords</H4>

Keywords are similar to Message Status, but they are chosen by the user.
Provided the mail server allows for it, you may add a set of possible keywords
to a folder and then you may set those keywords or not for each message
in the folder.
The syntax of this part of the Pattern is similar to the header patterns.
It is a list of keywords.
The Keyword part of the Pattern is a match if the message has any of
the keywords in the list set.
Like other parts of the Pattern, if this is unset it will be ignored.

<H4>Message Character Set</H4>

A message may use one or more character sets.
This part of the Pattern matches messages which make use of one or more of
the character sets specified in the pattern.
It will be considered a match if a message uses any of the character
sets in the list you give here.
The syntax of this part of the Pattern is similar to the header patterns
and the Message Keywords pattern.
It is a list of character sets.

<P>
Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
GB2312) you may also use some shorthand names that <EM>Alpine</EM> provides.
These names are more understandable shorthand names for sets of 
character set names.
Two examples are &quot;Cyrillic&quot; and &quot;Greek&quot;.
Selecting one of these shorthand names is equivalent to selecting all of
the character sets that make up the set.
You can see all of these shorthand names and the lists of character sets
they stand for by typing the &quot;T&quot; command with the Character
Set pattern highlighted.
The Character Set part of the Pattern is a match if the message uses any
of the character sets in the list.
Like other parts of the Pattern, if this is unset it will be ignored.

<H4>Raw 8-bit in Subject</H4>

It seems that lots of unwanted email contains unencoded 8-bit characters
in the Subject.
Normally, characters with the 8th bit set are not allowed in the Subject
header unless they are MIME-encoded.
This option gives you a way to match messages which have Subjects which
contain unencoded 8-bit characters.
Setting this option will affect performance in large folders because the
subject of each message in the folder has to be checked.

<H4>Beginning of Month</H4>

This option gives you a way to take some action once per month.
The value &quot;Yes&quot; means that this must be the first time <EM>Alpine</EM> has
been run this month in order to count as a match,

<H4>Beginning of Year</H4>

This option gives you a way to take some action once per year.
The value &quot;Yes&quot; means that this must be the first time <EM>Alpine</EM> has
been run this year in order to count as a match,

<H4>From or Reply-To address in Address Books</H4>

This option gives you a way to match messages which have a From or
a Reply-To address
which is in one of your address books.
Only the simple entries in your address books are searched.
Address book distribution lists are ignored!
Setting this option will affect performance in large folders because the
From and Reply-To of each message in the folder have to be checked.

<H4>Categorizer Command</H4>

This is a command that is run with its standard input set to the message
being checked and its standard output discarded.
The full directory path should be specified.
The command will be run and then its exit status will be checked against
the Exit Status Interval, which defaults to just the value zero.
If the exit status of the command falls in the interval, it is considered
a match, otherwise it is not a match.
<P>

This option may actually be a list of commands.
The first one that exists and is executable is used.
That makes it possible to use the same configuration with Unix <EM>Alpine</EM> and
<EM>PC-Alpine</EM>.
<P>

If none of the commands in the list exists and is executable then the rule
is <EM>not</EM> a match.
If it is possible that the command may not exist, you should be careful
to structure your rules so that nothing destructive
happens when the command does not exist.
For example, you might have a filter that filters away spam when there is
a match but does nothing when there is not a match.
That would continue to work correctly if the command didn't exist.
However, if you have a filter which filters away spam when there is not
a match and keeps it when there is a match, that would filter everything
if the categorizer command didn't exist.

<H3><A NAME="help-for-pattern-config"></A>Help Configuring Pattern Fields</H3>

<DL COMPACT>

<DT> <A NAME="role-nickname"><EM>Nickname</EM></A>

<DD> This is a nickname to help you.
You should have a different nickname for each role you define.
The nickname will be used in the SETUP ROLE RULES screen to allow you to
pick a role to edit.
It will also be used when you send a message to let you know you are
sending with a different role than you use by default, and
it will be useful for choosing a role when composing with the Role command
or when composing with one of the Role Uses set to With Confirmation.
This field is not used in the outgoing message.
<P>

<DT> <A NAME="role-comment"><EM>Comment</EM></A>

<DD> This is a comment to help you.
This comment does not play any functional role, it is simply an optional
comment to help you remember what the rule is for.
<P>

<DT> <A NAME="to-pattern"><EM>To pattern</EM></A>

<DD> If this pattern is non-blank, then for this role to be considered a
match, at least one of the recipients from
the To line of the message being replied to or forwarded
must match this pattern.
In the case of the Compose command, this pattern and the other header
patterns are ignored.
If this pattern is a list of patterns, then at least one of the
recipients must match at least one of the patterns.
(Any other non-blank parts of the Pattern must match, too.)
If the message being replied to or forwarded has a Resent-To header line,
then that is used in place of the To line.
(Note that this special Resent rule only applies to the To header. The
Resent-From, Resent-Subject, and so on are not consulted.)
<P>
It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
&quot;!&quot; &quot;toggle NOT&quot; command.
This changes the meaning of the To pattern so that it has the opposite meaning.
It will be considered a match if there are no matches between the
addresses in the To: line and the list of To patterns.
<P>
Don't make the mistake of putting the &quot;!&quot; in the data field for
the pattern.
For example, if you type the characters &quot;!frizzle&quot; into the To
pattern, the pattern will look like:
<P>
<PRE>
 To pattern = !frizzle
</PRE>
<P>
This means you want to match the 8 character sequence &quot;!frizzle&quot;.
In order to match messages which do not have &quot;frizzle&quot; in
their To field, first type the characters &quot;frizzle&quot; followed
by carriage return for the value of the To pattern, then negate it
by typing the &quot;!&quot; command.
It should end up looking like
<P>
<PRE>
 ! To pattern = frizzle
</PRE>
<P>

<DT> <A NAME="from-pattern"><EM>From pattern</EM></A>

<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the address from the From header of the message being replied to or forwarded instead
of the addresses from the To header.
<P>

<DT> <A NAME="sender-pattern"><EM>Sender pattern</EM></A>

<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the address from the Sender header of the message being replied to or forwarded instead
of the addresses from the To header.
If there is no Sender header, then the From header is used instead.
<P>

<DT> <A NAME="cc-pattern"><EM>Cc pattern</EM></A>

<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the address from the CC header of the message being replied to or forwarded instead
of the addresses from the To header.
<P>

<DT> <A NAME="news-pattern"><EM>News pattern</EM></A>

<DD> If this pattern is non-blank, then for this role to be considered a
match, at least one of the newsgroups from
the Newsgroups line of the message must match this pattern.
If this pattern is a list of patterns, then at least one of the
newsgroups must match at least one of the patterns.
(Any other non-blank parts of the Pattern must match, too.)
<P>

<DT> <A NAME="subject-pattern"><EM>Subject pattern</EM></A>

<DD> This is similar to the other header patterns.
It is compared with
the contents from the Subject of the message being replied to or forwarded.
<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="#char-set">Character-Set</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>

<DT> <A NAME="extra-header-patterns"><EM>Extra header patterns</EM></A>

<DD> There isn't actually a field called Extra header patterns, but you
may add extra header patterns by moving the cursor to one of the header
patterns and using the &quot;eXtraHdr&quot; command to add a new header
pattern.
You would do this if the six predefined header patterns don't cover the
header you want to use for pattern matching.
Once you've added an extra header pattern, you use it just like the
Subject pattern.
Of course, it is compared with
the contents from the particular header field of the message being replied
to or forwarded rather than the contents from the subject field.
To remove an extra header pattern from a role, use the &quotRemoveHdr&quot;
command on the highlighted extra header.
<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="#char-set">Character-Set</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>

<DT> <A NAME="recip-pattern"><EM>Recipient pattern</EM></A>

<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the addresses from both the To header and the Cc header
instead of just the addresses from the To header.
It's equivalent to having two different rules;
one with a To pattern and the other with the same Cc pattern.
<P>

<DT> <A NAME="partic-pattern"><EM>Participant pattern</EM></A>

<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the addresses from the To header, the Cc header, and the From header
instead of just the addresses from the To header.
It's equivalent to having three different rules;
one with a To pattern, another with the same Cc pattern, and another
with the same From pattern.
<P>

<DT> <A NAME="alltext-pattern"><EM>AllText pattern</EM></A>

<DD> This is similar to the header patterns.
Instead of comparing with text in a particular header field it is compared with
all of the text in the message header and body.
<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="#char-set">Character-Set</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>

<DT> <A NAME="bodytext-pattern"><EM>BodyText pattern</EM></A>

<DD> Just like AllText, except it is compared only with the body of the
message, not the body and header.

<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="#char-set">Character-Set</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>

<DT> <A NAME="age-interval"><EM>Age Interval</EM></A>

<DD>The Age Interval, if defined, is part of the Pattern.
If you use this, it should be set to something like:
<P>
<CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
<P>
where &quot;min_age&quot; and &quot;max_age&quot; are non-negative integers.
The special value &quot;INF&quot; may be used for the max value.
It represents infinity.
<P>
In rare cases it may be useful to use the more general form of the value,
which is a comma-separated list of intervals.
It would look something like:
<P>
<CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
<P>
When there is an Age Interval defined, it is a match if the age, in days, of
the message is contained in the interval.
The interval includes both endpoints.
If the option is set to a list of intervals then it is a match if the
age of the message is contained in any of the intervals.
<P>
Even though this option is called Age, it isn't actually
the <EM>age</EM> of the message.
Instead, it is how many days ago the message arrived in one of your folders.
If the current time is a little past midnight, then a message that arrived
just before midnight arrived yesterday, even though the message is only
a few minutes old.
By default, the date being used is not the date in the Date
header of the message.
It is the date that the message arrived in one of your folders.
When you Save a message from one folder to another that arrival date
is preserved.
If you would like to use the date in the Date header that is possible.
Turn on the option
<EM>use-date-header-for-age</EM>
near the bottom of the rule definition.
<P>
A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
The age interval
<P>
<CENTER><SAMP>(2,2)</SAMP></CENTER>
<P>
matches all messages that arrived on the day before yesterday.
The interval
<P>
<CENTER><SAMP>(180,INF)</SAMP></CENTER>
<P>
matches all messages that arrived at least 180 days before today.
The interval
<P>
<CENTER><SAMP>(0,1)</SAMP></CENTER>
<P>
matches all messages that arrived today or yesterday.
<P>

<DT> <A NAME="score-interval"><EM>Score Interval</EM></A>

<DD> The Score Interval, if defined, is part of the Pattern.
If you use this, it should be set to something like:
<P>
<CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
<P>
where &quot;min_score&quot; and &quot;max_score&quot; are integers between
-32000 and 32000.
The special values &quot;-INF&quot; and &quot;INF&quot; can be used for
the min and max values.
These represent negative and positive infinity.
<P>
Actually, the value may be a list of intervals rather than just a
single interval if that is useful.
The elements of the list are separated by commas like:
<P>
<CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
<P>
When there is a Score Interval defined, it is a match if the score for
the message is contained in any of the intervals.
The intervals include both endpoints.
The score for a message is calculated by looking at every scoring rule
defined and adding up the Score Values for the rules which match the message.
<P>

<DT> <A NAME="keyword-pattern"><EM>Keyword pattern</EM></A>

<DD> A folder may have user-defined keywords.
These are similar to the Important flag which the user may set using the
Flag command.
The difference is that the Important flag is always present for each folder.
User-defined keywords are picked by the user.
You may add new keywords by defining them in the
<A HREF="#keywords">Keywords</A> option in the Setup/Config screen.
After you have added a potential keyword with the Keywords option,
the Flag command may be used to set or clear the keyword on individual messages.
If you have given a keyword a nickname when configuring it,
that nickname may be used instead of the actual keyword.

<P>
When filling in a value for this field, it may be easiest to use
the &quot;T&quot; command, which presents you with a list of the keywords
you have defined to choose from.

<P>
This part of the Pattern matches messages with certain keywords set.
It will be considered a match if a message has any of the keywords in the
list set.

<P>
It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the
&quot;!&quot; &quot;toggle NOT&quot; command.
This changes the meaning of the Keyword pattern so that it has the opposite meaning.
It will be considered a match if none of the keywords in the list are set
for a message.
<P>
Don't make the mistake of putting the &quot;!&quot; in the data field for
the pattern.
For example, if you type the characters &quot;!frizzle&quot; into the Keyword
pattern, the pattern will look like:
<P>
<PRE>
 Keyword pattern = !frizzle
</PRE>
<P>
This means you want to match the 8 character sequence &quot;!frizzle&quot;.
In order to match messages which do not have the keyword &quot;frizzle&quot;
set, first type the characters &quot;frizzle&quot; followed
by carriage return for the value of the Keyword pattern, then negate it
by typing the &quot;!&quot; command.
It should end up looking like
<P>
<PRE>
 ! Keyword pattern = frizzle
</PRE>
<P>

<DT> <A NAME="charset-pattern"><EM>Character Set pattern</EM></A>

<DD> A message may use one or more character sets.
This part of the Pattern matches messages which make use of
certain specified character sets.
It will be considered a match if a message uses any of the character
sets in the list you give here.

<P>
When filling in a value for this field, you may use
the &quot;T&quot; command, which presents you with a large list of
possible character sets to choose from.
You may also just type in the name of a character set, and it need not
be one that Alpine knows about.

<P>
Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
GB2312) you may also use some shorthand names that Alpine provides.
These names are more understandable shorthand names for sets of 
character set names.
Two examples are &quot;Cyrillic&quot; and &quot;Greek&quot;.
Selecting one of these shorthand names is equivalent to selecting all of
the character sets that make up the set.
You can see all of these shorthand names and the lists of character sets
they stand for by typing the &quot;T&quot; command.

<P>
For the purposes of this Pattern,
<EM>Alpine</EM> will search through a message for all of the text parts and
collect the character sets declared for each part.
It will also look in the Subject line for a character set used there.
<EM>Alpine</EM> does not actually look at the text of the message or the text
of the Subject to determine if a declared character set is actually
used, it looks only at the declarations themselves in the MIME part headers
and in the Subject.

<P>
It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the
&quot;!&quot; &quot;toggle NOT&quot; command.
This changes the meaning of the Character Set pattern so that
it has the opposite meaning.
It will be considered a match if none of the character sets in the
list are used in a message.
<P>
Don't make the mistake of putting the &quot;!&quot; in the data field for
the pattern.
For example, if you type the characters &quot;!GB2312&quot; into the
Character Set pattern, the pattern will look like:
<P>
<PRE>
 Charset pattern = !GB2312
</PRE>
<P>
This means you want to match the 7 character sequence &quot;!GB2312&quot;.
In order to match messages which do not have the
character set &quot;GB2312&quot;
set, first type the characters &quot;GB2312&quot; followed
by carriage return for the value of the Character Set pattern, then negate it
by typing the &quot;!&quot; command.
It should end up looking like
<P>
<PRE>
 ! Charset pattern = GB2312
</PRE>
<P>
A technicality: Since comma is the character used to separate multiple
values in a pattern field, you have to escape comma with a backslash (&#92;) if
you want to include a literal comma in the field.
In other words, if you type a backslash followed by a comma it will
be interpreted as a comma by <EM>Alpine</EM>, instead of as a separator between
pattern values.
All other backslashes are literal backslashes and should not be escaped.
<P>

<DT> <A NAME="current-folder-type"><EM>Current Folder Type</EM></A>

<DD> The Current Folder Type is part of the Pattern.
It refers to the type of the currently open folder, which is the folder
you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen.
In order for a pattern to be considered a match, the current folder must
be of the type you set here.
The three types &quot;Any&quot;, &quot;News&quot;, and &quot;Email&quot; are
all what you might think.
<P>
If the Current Folder Type for a Pattern is set to &quot;News&quot;, for
example, then
that will only be a match if the current folder is a newsgroup and
the rest of the Pattern matches.
The value &quot;Specific&quot; may be used when you want to limit the match
to a specific folder (not just a specific type of folder), or to a list of
specific folders.
In order to match a specific folder you must Select the &quot;Specific&quot;
button <EM>AND</EM> you must fill in
the name (or list of names) of
the folder in the &quot;Folder&quot; field.
If the current folder is any of the folders in the list, that is considered
a match.
The name of each folder in the list may be either &quot;INBOX&quot;, the technical specification
of the folder (like what appears in your configuration file) or, if the
folder is one of your incoming folders, it may be the nickname you've given
the folder.
Here are a couple samples of specific folder names:
<P>
<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
<P>
<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
<P>
The easiest way to fill in the &quot;Folder&quot; field is to use
the T command which is available when the &quot;Folder&quot; line is
highlighted.
Note that you won't be able to edit the &quot;Folder&quot; line unless the
Current Folder Type is set to &quot;Specific&quot;, and any value that
&quot;Folder&quot; has is ignored unless the type
is set to &quot;Specific&quot;.
<P>
When reading a newsgroup, there may be a performance penalty
incurred when collecting the information necessary to check a Pattern.
For this reason, the default Current Folder Type is set to &quot;Email&quot;.
For example, a role with a non-Normal Index Line Color
and a Current Folder Type of
&quot;Any&quot; or &quot;News&quot; may cause the MESSAGE INDEX
screen to draw more slowly when in a newsgroup.
<P>

<DT> <A NAME="message-status-important"><EM>Message Status Important</EM></A>

<DD> This part of the Pattern may have one of three possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The other two values are &quot;Yes&quot;, which means the message must be
flagged &quot;Important&quot; in order to be a match; or &quot;No&quot;, which
means the message must <EM>not</EM> be flagged &quot;Important&quot; in order
to be considered a match.
<P>

<DT> <A NAME="message-status-new"><EM>Message Status New</EM></A>

<DD> This part of the Pattern may have one of three possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The other two values are &quot;Yes&quot;, which means the message must be
&quot;New&quot; in order to be a match; or &quot;No&quot;, which
means the message must <EM>not</EM> be &quot;New&quot; in order
to be a match.
&quot;New&quot; is the same as <EM>Unseen</EM> and not &quot;New&quot; is the
same as <EM>Seen</EM>.
<P>
The nomenclature for New and Recent is a bit confusing:
<P>
New means that the message is Unseen.
It could have been in your mailbox for a long time but if you haven't looked
at it, it is still considered New.
That matches the default <EM>Alpine</EM> index display that shows an N for such a
message.
<P>
Recent means that the message was added to this folder since the last time
you opened the folder.
<EM>Alpine</EM> also shows an N by default for these types of messages.
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after
the other, a message would only show up as Recent in (at most) the first
<EM>Alpine</EM> session.
<P>

<DT> <A NAME="message-status-recent"><EM>Message Status Recent</EM></A>

<DD> This part of the Pattern may have one of three possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The other two values are &quot;Yes&quot;, which means the message must be
&quot;Recent&quot; in order to be a match; or &quot;No&quot;, which
means the message must <EM>not</EM> be &quot;Recent&quot; in order
to be a match.
&quot;Recent&quot; means that the message was added to the folder since
the last time the folder was opened.
If more than one mail client has the folder opened, the message will
appear to be &quot;Recent&quot; to only one of the clients.
<P>
The nomenclature for New and Recent is a bit confusing:
<P>
New means that the message is Unseen.
It could have been in your mailbox for a long time but if you haven't looked
at it, it is still considered New.
That matches the default <EM>Alpine</EM> index display that shows an N for such a
message.
<P>
Recent means that the message was added to this folder since the last time
you opened the folder.
<EM>Alpine</EM> also shows an N by default for these types of messages.
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after
the other, a message would only show up as Recent in (at most) the first
<EM>Alpine</EM> session.
<P>

<DT> <A NAME="message-status-deleted"><EM>Message Status Deleted</EM></A>

<DD> This part of the Pattern may have one of three possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The other two values are &quot;Yes&quot;, which means the message must be
marked &quot;Deleted&quot; in order to be a match; or &quot;No&quot;, which
means the message must <EM>not</EM> be marked &quot;Deleted&quot; in order
to be a match.
<P>
If you are thinking of using this part of the Pattern as a way to prevent
messages from being filtered more than once in a Filter Pattern,
take a look at the Filter Option
<A HREF="#move-only-if-not-deleted">&quot;move-only-if-not-deleted&quot;</A>
instead.
It should work better than using this field since it will hide the filtered
messages even if they are already Deleted.
<P>

<DT> <A NAME="message-status-answered"><EM>Message Status Answered</EM></A>

<DD> This part of the Pattern may have one of three possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The other two values are &quot;Yes&quot;, which means the message must be
marked &quot;Answered&quot; in order to be a match; or &quot;No&quot;, which
means the message must <EM>not</EM> be marked &quot;Answered&quot; in order
to be a match.
<P>

<DT> <A NAME="subject-contains-raw-8bit"><EM>Subject Contains Raw 8-bit</EM></A>

<DD> This part of the Pattern may have one of three possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The other two values are &quot;Yes&quot;, which means the Subject of
the message must contain unencoded 8-bit characters (characters with the
most significant bit set)
in order to be a match; or &quot;No&quot;, which
means the Subject must <EM>not</EM>
contain unencoded 8-bit characters in order to be a match.
<P>

<DT> <A NAME="beginning-of-month"><EM>Beginning of Month</EM></A>

<DD> This part of the Pattern may have one of three possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The other two values are &quot;Yes&quot;, which means this is the first
time <EM>Alpine</EM> has been run this month;
or &quot;No&quot;, which
means this is <EM>not</EM> the first time <EM>Alpine</EM> has been run this month.
The way that <EM>Alpine</EM> decides if it is the beginning of the month or not is
to compare today's date with the date stored in the
<A HREF="#last-time">Last-Time-Prune-Questioned</A>
variable in the config file.
If the month of today's date is later than the month stored in the variable,
then this is considered to be the first time you have run Alpine this month, and
that turns the Beginning of the Month option on.
<P>

<DT> <A NAME="beginning-of-year"><EM>Beginning of Year</EM></A>

<DD> This part of the Pattern may have one of three possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The other two values are &quot;Yes&quot;, which means this is the first
time <EM>Alpine</EM> has been run this year;
or &quot;No&quot;, which
means this is <EM>not</EM> the first time <EM>Alpine</EM> has been run this year.
The way that <EM>Alpine</EM> decides if it is the beginning of the year or not is
to compare today's date with the date stored in the
<A HREF="#last-time">Last-Time-Prune-Questioned</A>
variable in the config file.
If the year of today's date is later than the year stored in the variable,
then this is considered to be the first time you have run Alpine this year, and
that turns the Beginning of the Year option on.
<P>

<DT> <A NAME="from-in-abook"><EM>From or Reply-To in Address Book</EM></A>

<DD> This part of the Pattern may have one of five possible values.
The default value is &quot;Don't care&quot;, which matches any message.
The value &quot;Yes, in any address book&quot; means either the From address
or the Reply-To address of the message must be in at least one of your
address books in order to be a match.
The value &quot;No, not in any address book&quot;
means neither the From nor the Reply-To addresses may
be in any of your address books in order to be a match.
<P>
The values &quot;Yes, in specific address books&quot; and
&quot;No, not in any of specific address books&quot; are similar but instead
of depending on all address books you are allowed to give a list of address
books to look in.
Usually this would be a single address book but it may be a
list of address books as well.
For each of these &quot;specific&quot; address book options you Select which
of the Specific options you want (Yes or No) <EM>AND</EM> fill in the
name (or list of names) of the address book in the
&quot;Abook List&quot; field.
The names to be used are those that appear in the ADDRESS BOOK LIST screen.
The easiest way to fill in the Abook List field it to use
the &quot;T&quot; command which is available when the &quot;Abook List&quot;
line is highlighted.
Note that you won't be able to edit the &quot;Abook List&quot; line unless the
option is set to one of the two &quot;Specific&quot;, values.
<P>

<DT> <A NAME="categorizer-cmd-explained"><EM>Categorizer Command</EM></A>

<DD> This is a command that is run with its standard input set to the message
being checked and its standard output discarded.
The full directory path should be specified.
The command will be run and then its exit status will be checked against
the <EM>Exit Status Interval</EM>, which defaults to just the value zero.
If the exit status of the command falls in the interval, it is considered
a match, otherwise it is not a match.
<P>

This option may actually be a list of commands.
The first one that exists and is executable is used.
That makes it possible to use the same configuration with Unix <EM>Alpine</EM> and
<EM>PC-Alpine</EM>.
<P>

If none of the commands in the list exists and is executable then the rule
is <EM>not</EM> a match.
If it is possible that the command may not exist, you should be careful
to structure your rules so that nothing destructive
happens when the command does not exist.
For example, you might have a filter that filters away spam when there is
a match but does nothing when there is not a match.
That would continue to work correctly if the command didn't exist.
However, if you have a filter which filters away spam when there is not
a match and keeps it when there is a match, that would filter everything
if the categorizer command didn't exist.
<P>

The categorizer command is run and the result is the exit status of
that command.
If that exit status falls in the <EM>Exit Status Interval</EM>
then it is considered a match, otherwise it is not a match.
Of course for the entire rule to match, it must also be checked against
the other defined parts of the Pattern.
<P>
The <EM>Exit Status Interval</EM> defaults to the single value 0 (zero).
If you define it, it should be set to something like:
<P>
<CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER>
<P>
where &quot;min_exit_value&quot; and &quot;max_exit_value&quot; are integers.
The special values &quot;INF&quot; and &quot;-INF&quot; may be used for large
positive and negative integers.
<P>
Actually, a list of intervals may be used if you wish.
A list would look like
<P>
<CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER>
<P>
When there is an <EM>Exit Status Interval</EM> defined, it is a match if the exit status
of the categorizer command is contained in any of the intervals.
The intervals include both endpoints.
<P>
The default interval is
<P>
<CENTER><SAMP>(0,0)</SAMP></CENTER>
<P>
and it matches only if the command exits with exit status equal to zero.
<P>
It is also possible to set a <EM>Character Limit</EM> for the categorizer command.
Setting this option makes it possible to limit how much of the message
is made available to the categorizer command as input.
The default value (-1) means that the entire message is fed to the
command.
A value of 0 (zero) means that only the headers of the message are
made available.
A positive integer means that the headers plus that many characters from
the body of the message are passed to the categorizer.
<P>

</DL>

<H2><A NAME="configuring-news"></A>Configuring News</H2>

<EM>Alpine</EM> can access news folders in any one of three different ways:
<DL>
<DT>REMOTE NNTP</DT>
<DD>Using the Network News Transport Protocol (NNTP) to
access news on a remote news server.  In this case the newsrc file is
stored on the machine where <EM>Alpine</EM> is running.

<P>
To specify a remote news-collection accessed via NNTP use the
SETUP/collectionList screen's &quot;Add&quot; command.  Set the
Server: value to the NNTP server's hostname appended with the
communication method &quot;/service=NNTP&quot;, and set the Path:
value to the &quot;#news.&quot; namespace (without the quotes).
<P>
Instead of specifying a news-collection, you may simply set the
<A HREF="#nntp-server">nntp-server</A>
option, which will cause <EM>Alpine</EM> to create a default news-collection for you.
Another NNTP option which may be of interest is
<A HREF="#nntp-range">nntp-range</A>.

<DT>REMOTE IMAP</DT>
<DD>Using the Internet Message Access Protocol (IMAP) to
access news on a remote news server.  In this case, your newsrc file is
stored on the news server, in your home directory, so you must have an
account on the news server, but you would be running <EM>Alpine</EM> on a different
machine.  The news server must be running an IMAPd server process. 

<P>
To specify a remote news-collection accessed via IMAP use the
SETUP/collectionList screen's &quot;Add&quot; command.  Set the
Server: value to the IMAP server's hostname, and set the Path: value
to the &quot;#news.&quot; namespace (without the quotes).

</DD>

<DT>LOCAL</DT>
<DD>Using local file access to the news database.  In this
case, your newsrc file is stored on the news server, in your home
directory, so you must have an account on the news server, and you would
be running <EM>Alpine</EM> on the same machine.

<P>
To specify a local news-collection use the SETUP/collectionList
screen's &quot;Add&quot; command.  Leave the Server: value blank, and
set the Path: value to the &quot;#news.&quot; namespace (without the
quotes).

</DD>
</DL>

<P>

NOTE: Should no news-collection be defined as above, <EM>Alpine</EM> will
automatically create one using the Setup/Config screen's
&quot;nntp-server&quot; variable's value if defined.  The collection
will be created as a &quot;Remote NNTP&quot; as described above.

<P>

If you are a <EM>PC-Alpine</EM> user, either option 1 (NNTP) or option 2 (IMAP) is
possible.  If you don't have an account on the news server, or if the news
server is not running an IMAP daemon, then you must use NNTP.  (If you are not
sure, ask your service provider, university, or company for help.)  In
this case, your Unix .newsrc file can be transferred to your PC.  A good
place to put it would be in the same directory as your PINERC file, under
the name NEWSRC, but you can 
<A HREF="#newsrc-path">specify a different location</A>.

<P>
Other configuration features related to news are
<A HREF="#enable-8bit-nntp-posting">Enable-8bit-Nntp-Posting</A>.
<A HREF="#compose-sets-newsgroup-without-confirm">Compose-Sets-Newsgroup-Without-Confirm</A>,
<A HREF="#news-approximates-new-status">News-Approximates-New-Status</A>,
<A HREF="#news-deletes-across-groups">News-Deletes-Across-Groups</A>,
<A HREF="#news-offers-catchup-on-close">News-Offers-Catchup-On-Close</A>,
<A HREF="#news-post-without-validation">News-Post-Without-Validation</A>,
<A HREF="#news-read-in-newsrc-order">News-Read-in-Newsrc-Order</A>, and
<A HREF="#quell-extra-post-prompt">Quell-Extra-Post-Prompt</A>.

<HR>

<!-- pnuts -->

</BODY>
</HTML>
